This is an old revision of the document! Table of ContentsRelease ProcessPlan the Release
Test a Release BuildDo a Release build and a few sanity checks to make sure nothing is broken. Update Release NotesMake a note of the svn revision of the last release. E.g. for release 14.02, the revision according to the tags was 13662. (Note that this might not match up since the tags can be made long after the release. However, with the current build script this should only be “off by one” from the actual revision.) At the command line, use svn log to find out the current revision: $ svn log -l1 ------------------------------------------------------------------------ r13710 | tedfelix | 2014-06-03 15:46:54 -0400 (Tue, 03 Jun 2014) | 4 lines Set note-off velocity to 64 As recommended by the MIDI spec. See bug #1426. ------------------------------------------------------------------------ In a working copy, do an svn log to see the log entries since that revision. svn log -r 13662:13710 Or, on the sourceforge site: Code > trunk > rosegarden: http://sourceforge.net/p/rosegarden/code/HEAD/tree/trunk/rosegarden/ Then click the “History” button in the upper right. The list is in reverse order, so scroll down to the revision of the last release. Then work your way up through the commits. Update the release notes to reflect the commits since the last release. http://www.rosegardenmusic.com/wiki/dev:next_version When finished, move the release notes from the “Upcoming Release” page on the wiki to an official versioned release notes page on the wiki. Consider including the release notes within the tarball in the future. Maybe just accumulate them in a single file. What do other projects do? Changelog! Update the READMEUpdate copyright year as needed. Update anything else that seems like it needs updating. Update data.qrcRun “scripts/rebuild-qrc” to make sure the data.qrc file is up-to-date. Update CMakeLists.txtCheck/adjust the codename/version number in CMakeLists.txt. The codename/version number will be bumped after delivery. Commit Changessvn commit -m "Updates for version xx.xx" Create tarballUse the make-release-tarball script: scripts/make-release-tarball RELEASE Sanity test the tarball. Build and run from it. DeliverSee acpid release process for details.
Update WebsiteUpdate the website to point to the new version. The website can be updated by committing changes to the website directory in svn. These are automatically uploaded to the web server.
Test, commit, and test. See https://sourceforge.net/p/rosegarden/code/14701/ for an example. Update CMakeLists.txtBump the version number and codename. Commit. Announce
See also |