On the day of the string freeze, update the .ts files for the translators. Use Qt4 to make sure the resulting .ts files can be edited by translators using Qt4.
$ QT_SELECT=qt4 scripts/make-ts
Commit this and then announce the string freeze/start of the translation period.
On the eve of the release, send out a reminder for any last minute contributions and translations.
Check email for any pending changes or requests that need to be included in this release. Make those changes as appropriate.
Determine whether any changes have been made to the .rg file format. If so, decide the extent of those changes and what level of file format version update is required. Update the file format version as appropriate. See comments on FILE_FORMAT_VERSION_POINT in RosegardenDocument.cpp.
Changing the point version has no effect on anything as it is ignored. Changing the minor version will cause an “incompatibilities” warning on load, but the file will be loaded. Use this when data might be lost when opening a file with an older version of rg (e.g. new fields have been added). Changing the major version will cause older versions of rg to refuse to load the file. Obviously, we should avoid this at all costs. The chances are good that we will never have to do this.
On the release date, do a Release build and a few sanity checks to make sure nothing is broken.
Make 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.)
In a working copy, do an svn log to see the log entries from the previous release to the latest.
$ svn log -v -r 13662:HEAD | less
An alternative would be to browse the commits on sourceforge. I find it cumbersome, however.
Update the release notes to reflect the commits since the last release.
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 copyright year as needed.
Update anything else that seems like it needs updating.
Run “scripts/rebuild-qrc” to make sure the data.qrc file is up-to-date.
Check/adjust the code name/version number in CMakeLists.txt.
The code name/version number will be bumped after delivery, so this should be OK.
svn commit -m "Updates for version xx.xx"
Use the make-release-tarball script:
Sanity test the tarball. Build and run from it.
The make-release-tarball script will tag the release from trunk. This is correct for non-point releases.
For point releases, we need to tag the release from the stable branch:
svn copy svn+ssh://firstname.lastname@example.org/p/rosegarden/code/branches/stable-17.12 \ svn+ssh://email@example.com/p/rosegarden/code/tags/rosegarden-17.12.1 \ -m "Tag release 17.12.1"
We might upgrade make-release-tarball to accept a “POINT” option that will change the tagging behavior. Or we might be able to parse the output of svn info and use that to generate the two URLs for tagging. That should fix the 502 errors.
An “Unexpected HTTP status 502 'Bad Gateway'” error indicates that the URL used to create the tag doesn't match the URL used to checkout the repo. Use svn info to figure out what URL type to use:
$ svn info . ... URL: svn+ssh://firstname.lastname@example.org/p/rosegarden/code/branches/stable-17.12 Relative URL: ^/branches/stable-17.12 Repository Root: svn+ssh://email@example.com/p/rosegarden/code ...
From the above we know that we need to use an “svn+ssh” style URL to create a tag.
Update 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. The webpages use Server Side Includes (SSI), so you'll need to set up a web server to test before uploading changes.
Test, commit, wait for the auto upload (takes a while), and test.
See https://sourceforge.net/p/rosegarden/code/14701/ for an example.
Bump the version number and codename.
Discussion uses 17.12.1 as an example.
In svn a tag will move if you commit to it, so we will need to create a stable-17.12 branch from 17.12 so that we can make changes. Then we can do the usual tagging process on that branch to tag it for release.
svn copy https://svn.code.sf.net/p/rosegarden/code/tags/rosegarden-17.12 \ https://svn.code.sf.net/p/rosegarden/code/branches/stable-17.12 \ -m "Create stable-17.12 branch."
Checkout stable-17.12 someplace. Replace “tedfelix” with your sf userid.
svn checkout --username=tedfelix \ svn+ssh://firstname.lastname@example.org/p/rosegarden/code/branches/stable-17.12 \ stable-17.12
Cherrypick the various commits you need into the stable branch. Use svn merge to cherrypick. Cherrypicking a single commit:
svn merge -c 15189 ^/trunk/rosegarden
You'll need to commit that. Since svn doesn't bring in any information from the original commits, you'll want to include a list of revisions in the commit message. Format them with square brackets to get hyperlinks in sf: [r15189].
Finally, go back through the release process with the following changes: