Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
dev:release_process [2022/12/07 12:45] tedfelix [File Format Version] |
dev:release_process [2023/12/06 12:58] (current) tedfelix [Deliver] |
You can examine the commit history since the previous release in git using the command line: | You can examine the commit history since the previous release in git using the command line: |
| |
$ git log --stat --reverse 21.06..master | $ git checkout master |
| $ git log --stat --reverse 22.12.. |
| |
...or by using gitk. With gitk, you can enter the last release number in the "SHA1 ID:" field and it will jump to that tag. Then work your way backwards (up). | ...or by using gitk. With gitk, you can enter the last release number in the "SHA1 ID:" field and it will jump to that tag. Then work your way backwards (up). |
| |
* From a debug build, do ''make test'' to run unit tests. | * From a debug build, do ''make test'' to run unit tests. |
| * The tests may fail due to ASAN. grep for Totals to see the actual results: |
| |
| <file> |
| $ grep Totals Testing/Temporary/LastTest.log |
| </file> |
| |
* Do a Release build and a regression test. | * Do a Release build and a regression test. |
| |
| |
* Add any new changes to the CHANGELOG. | * Add any new changes to the CHANGELOG. |
* Copy the latest version of the CHANGELOG to a new page [[:start#release_notes|on the wiki]]. | * Copy the latest version of the CHANGELOG to the wiki. |
| |
===== Turn Off Logging ===== | ===== Turn Off Logging ===== |
| |
===== Update data.qrc ===== | ===== Update data.qrc ===== |
| |
| Get the latest yoshimi.rgd file from https://github.com/lorenzosu/rosegarden_yoshimi_banks/ |
| |
| Copy it to data/library and make sure it is all lower-case "yoshimi.rgd" to match the previous version. |
| |
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. |
- Upload the tarball to sf | - Upload the tarball to sf |
- Upload the current version section of the CHANGELOG to sf as README. | - Upload the current version section of the CHANGELOG to sf as README. |
- Update sourceforge to point to the new version. Use the "i" icon to the right of the file. Set "Default Download For:" to Tux. Set "Download Button:" text to "Rosegarden xx.xx". | - Update sourceforge to point to the new version. Use the "i" icon to the right of the file. Set "Default Download For:" to Tux. |
| |
===== Update Website ===== | ===== Update Website ===== |
===== Point Release Process ===== | ===== Point Release Process ===== |
| |
//Discussion uses 21.06.1 as an example.// | //Discussion uses 22.12.1 as an example.// |
| |
Check out a "point" branch based on the tag you want to start at. | Create a new stable branch based on the tag you want to start at. |
| |
git checkout -b point 21.06 | git checkout -b 22.12-stable 22.12 |
| |
Cherry-pick any commits you need. | Cherry-pick any commits you need from master. |
| |
git cherry-pick 9713720e | |
| |
Go back through the release process carefully. Some things to watch out for: | Go back through the release process carefully. Some things to watch out for: |
- Update the CHANGELOG notes with a complete new point release. | - Update the CHANGELOG notes with a complete new point release. |
- Version will need to be adjusted in CMakeLists.txt. | - Version will need to be adjusted in CMakeLists.txt. |
- You will need to push the point branch in order to generate a tarball. You can always delete it later. | - You will need to push the stable branch in order to generate a tarball. |
- No need for a new version directory on sf. | - No need for a new version directory on sf. |
- No need to bump the version number after the tarball. | - No need to bump the version number after the tarball. |
| |
Delete the point branch local and remote once the tags are pushed. | |
| |
===== See also ===== | ===== See also ===== |