Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:release_process [2018/02/14 14:41]
tedfelix |
dev:release_process [2018/02/17 04:17]
tedfelix [Tagging the Release] |
| Sanity test the tarball. Build and run from it. | Sanity test the tarball. Build and run from it. |
| |
| | ==== Tagging the Release ==== |
| | |
| | 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+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.// |
| | ==== Tagging 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://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. |
| |
| ===== Deliver ===== | ===== Deliver ===== |
