Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:release_process [2018/02/17 03:40] tedfelix [Create tarball] |
dev:release_process [2018/05/30 12:52] tedfelix [String Freeze] |
$ QT_SELECT=qt4 scripts/make-ts | $ QT_SELECT=qt4 scripts/make-ts |
| |
Commit this and then announce the string freeze/start of the translation period. | Commit this: |
| |
| svn commit -m "Update .ts files for xx.xx (scripts/make-ts)" |
| |
| Announce the string freeze/start of the translation period. |
| |
===== Release Eve ===== | ===== Release Eve ===== |
| |
Check email for any pending changes or requests that need to be included in this release. Make those changes as appropriate. | Check email for any pending changes or requests that need to be included in this release. Make those changes as appropriate. |
| |
| |
| ===== File Format Version ===== |
| |
| 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. |
| |
| |
==== Tagging the Release ==== | ==== Tagging the Release ==== |
| |
The make-release-tarball script will attempt to tag the release for you. In some cases, you will need to do this differently. For a point release, the make-release-tarball script creates the tag from trunk rather than the stable branch. You'll need to tag a point release manually like this: | 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://tedfelix@svn.code.sf.net/p/rosegarden/code/branches/stable-17.12 \ | svn copy svn+ssh://tedfelix@svn.code.sf.net/p/rosegarden/code/branches/stable-17.12 \ |
-m "Tag release 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.// |
==== Tagging Errors ==== | ==== Tagging Errors ==== |
| |