| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:release_process [2018/02/17 04:17]
tedfelix [Tagging the Release] |
dev:release_process [2018/12/13 03:52]
tedfelix [Tagging Errors] |
| ===== String Freeze ===== | ===== String Freeze ===== |
| |
| 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. | On the day of the string freeze, update the .ts files for the translators. We are now standardized on Qt5, so make sure that is the current version of Qt. |
| |
| $ QT_SELECT=qt4 scripts/make-ts | $ QT_SELECT=qt5 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 ===== |
| |
| |
| ===== Test a Release Build ===== | ===== File Format Version ===== |
| |
| On the release date, do a Release build and a few sanity checks to make sure nothing is broken. | 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. |
| | |
| | |
| | ===== Test a Release Build ===== |
| | |
| | On the release date, do a couple of Release builds and a few sanity checks to make sure nothing is broken. |
| |
| ===== Update Release Notes ===== | ===== Update Release Notes ===== |
| |
| ===== Commit Changes ===== | ===== Commit Changes ===== |
| | |
| | If needed: |
| |
| svn commit -m "Updates for version xx.xx" | svn commit -m "Updates for version xx.xx" |
| |
| From the above we know that we need to use an "svn+ssh" style URL to create a tag. | From the above we know that we need to use an "svn+ssh" style URL to create a tag. |
| | |
| | Any errors related to a "wallet" can safely be ignored and the wallet UI can safely be closed via the "cancel" button. |
| |
| ===== Deliver ===== | ===== Deliver ===== |
