Project: datamanagement
Issue DM-1632: Build 2014_11 Qserv release
The title says it all. Please open ticket for next release when closing this one. Tasks to do: - publish last buildbot build under a temporary eups-tag ("qserv-dev")and test it, if it works fine: - create git-tags for Qserv and dependencies - publish the release with eups-tags "qserv" and "YYYY_MM" - generate and publish the doc for release "YYYY_MM" - update release number in Qserv code and set "YYYY_MM+1" as release in dev and "YYYY_MM" as stable release (update {{admin/bin/qserv-version.sh}}, {{doc/source/conf.py}}, {{doc/source/toplevel.rst}}) - generate and publish the doc for release "YYYY_MM+1" - look at the doc - commit {{admin/bin/qserv-version.sh}}, {{doc/source/conf.py}}, {{doc/source/toplevel.rst}} with current ticket number This procedure should be validated and documented.
Story points: 1