Fixed problem with SPInfo and SPPrivacy URLS. Also changed name of /events/ view to 'home-events' so the 'home' view will point to the one that is actually public.

Removed 'crap' block from search view. Commented out timeline view, which is of ancient lineage and has not been used in the present age.

Removed 'Alpha' from the GraceDB homepage. Also added service provider privacy and info pages, which are required for federation with InCommon.

Removed SimpleSearchFormWithSubclasses. The only thing that needed this was the gstlalcbc report page, and there is a simple workaround instead: just get a list of Event objects, and upcast them to CoincInspiralEvents. One wrinkle is that the matplotlib call 'fill_between' (which had given us that nice grey region on either side of the expected IFAR line) seems to hang now. I emailed Chad and commented this out.

Fixed URL sent out in event creation LVAlert to a valid URL, namely the URL of the event file in the web interface.

Added some features to gstlalcbc_report (semi-adaptive mass bins, default query, end_time template filter). Also refactored gstlalcbc_report into reports.py. Some other cleaning up.

Modified translator for CWB events to consume links to the CED and FITS skymap, if available, and write log messages with the links. Resolves Issue #1179.

Added migrations for gdb_pe robot cert and 'background' tag. Also added 'background' to the list of blessed tags in the settings module.

Fixed handle_uploaded_data to check whether the likelihood column is inf. Replaces 'inf' with the largest value that can be accepted by the mysql database. Fixes issue 1171. But we might find ourselves needing to check other columns in the future.

Fix for Issue #975, 'Versioned files displaying only newest versions in event detail page'. To fix this, we add a file_version field to the event log. This is accessed from the VersionedFile object at the time of file-saving. That way, the correct version can always be associated with any given log message.

Made changes to bring VOEvent closer in-line with what Mina and Peter are proposing. However, I still don't have their AlertVersion property. Nor do I have any of the analysis specific stuff, like ChripMass, frequency, etc.

analyst_comments and data_quality tags are blessed,
 but were not in the fixture for tags.