| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:release_process [2020/12/09 14:11]
tedfelix [Feature Freeze] |
dev:release_process [2021/04/06 03:16]
tedfelix |
| * Send a "Testing Appreciated" email to the user list. | * Send a "Testing Appreciated" email to the user list. |
| * Make a "Testing Appreciated" post on f-book. | * Make a "Testing Appreciated" post on f-book. |
| | * Run the unit tests with ''make test''. |
| | * Perform a regression test. |
| |
| ===== String Freeze ===== | ===== String Freeze ===== |
| |
| |
| ===== Test a Release Build ===== | ===== Testing ===== |
| |
| On the release date, do a Release build and a few sanity checks to make sure nothing obvious is broken. | On the release date... |
| | |
| | * From a debug build, do ''make test'' to run unit tests. |
| | * Do a Release build and a regression test. |
| |
| ===== Update CHANGELOG ===== | ===== Update CHANGELOG ===== |
| data/appdata/rosegarden.appdata.xml | data/appdata/rosegarden.appdata.xml |
| |
| Validate with appdatacli: | Validate with appstreamcli: |
| |
| appstreamcli validate data/appdata/rosegarden.appdata.xml | appstreamcli validate data/appdata/rosegarden.appdata.xml |
| |
| Run "scripts/rebuild-qrc-nosvn" to make sure the data.qrc file is up-to-date. | Run "scripts/rebuild-qrc-nosvn" to make sure the data.qrc file is up-to-date. |
| |
| |
| ===== Check Code Name and Version ===== | ===== Check Code Name and Version ===== |
| Check/adjust the code name/version number in CMakeLists.txt. | 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.// | //The code name/version number should have been bumped after the last delivery, so this should be OK.// |
| |
| ===== Commit Changes ===== | ===== Commit Changes ===== |
| |
| svn commit -m "Updates for version xx.xx" | svn commit -m "Updates for version xx.xx" |
| |
| |
| ===== Create tarball ===== | ===== Create tarball ===== |
| |
| Use the make-release-tarball script: | Download a snapshot from the git repo page on SourceForge. |
| |
| scripts/make-release-tarball RELEASE | cd to where the snapshot was saved and run the make-release-tarball script with the name of the snapshot: |
| | |
| ==== Tagging the Release ==== | |
| |
| The make-release-tarball script will tag the release from trunk. This is correct for non-point releases. | <path-to-source>/scripts/make-release-tarball <snapshot-name>.zip |
| |
| For point releases, we need to tag the release from the stable branch: | ===== Tag the Release ===== |
| |
| svn copy svn+ssh://tedfelix@svn.code.sf.net/p/rosegarden/code/branches/stable-17.12 \ | From the sourcebase... |
| svn+ssh://tedfelix@svn.code.sf.net/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.// | git tag -m "Release" xx.xx |
| ==== Tagging Errors ==== | git push --tags |
| | |
| For some reason, I get a lot of errors during the tagging process. | |
| | |
| === Bad Gateway === | |
| | |
| 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://tedfelix@svn.code.sf.net/p/rosegarden/code/branches/stable-17.12 | |
| Relative URL: ^/branches/stable-17.12 | |
| Repository Root: svn+ssh://tedfelix@svn.code.sf.net/p/rosegarden/code | |
| ... | |
| | |
| From the above we know that we need to use an "svn+ssh" style URL to create a tag. | |
| | |
| === Password Prompts === | |
| | |
| It might prompt for password, you can cancel that. This might drop to the command line and prompt for a password. I usually enter it here and get a ton of errors related to trying to launch kwalletd. It still seems to work. | |
| | |
| === Wallet? === | |
| | |
| Any errors related to a "wallet" can safely be ignored and the wallet UI can safely be closed via the "cancel" button. | |
| |
| ===== Test tarball ===== | ===== Test tarball ===== |
| 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. | 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. |
| |
| * /website/getting/source/index.shtml (http://www.rosegardenmusic.com/getting/source/index.shtml) | * /website/index.shtml (http://www.rosegardenmusic.com/) |
| * Update link to the current stable release. | * Update version. |
| | * Update link to release notes on wiki. |
| |
| * /website/subleft.html (main page on the left) | * /website/subleft.html (main page on the left) |
| * Add a new "newsheadline". | * Add a new "newsheadline". |
| |
| * /website/index.shtml (http://www.rosegardenmusic.com/) | * /website/getting/source/index.shtml (http://www.rosegardenmusic.com/getting/source/index.shtml) |
| * Update version. | * Update link to the current stable release. |
| * <del>Copy in release notes summary.</del> | |
| * Update link to release notes on wiki. | |
| |
| * /website/latest-version.txt (http://www.rosegardenmusic.com/latest-version.txt) | * /website/latest-version.txt (http://www.rosegardenmusic.com/latest-version.txt) |
