Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:release_process [2018/12/13 04:53]
tedfelix
dev:release_process [2020/06/04 05:05] (current)
tedfelix [Update Website]
Line 40: Line 40:
 ===== Test a Release Build ===== ===== 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.+On the release date, do a Release ​build and a few sanity checks to make sure nothing ​obvious ​is broken.
  
-===== Update ​Release Notes =====+===== Update ​CHANGELOG ​=====
  
 Make a note of the svn revision of the last release. ​ E.g. for release 14.02, the revision according to the tags was 13662. ​ (Note that this might not match up since the tags can be made long after the release. ​ However, with the current build script this should only be "off by one" from the actual revision.) Make a note of the svn revision of the last release. ​ E.g. for release 14.02, the revision according to the tags was 13662. ​ (Note that this might not match up since the tags can be made long after the release. ​ However, with the current build script this should only be "off by one" from the actual revision.)
Line 52: Line 52:
 //An alternative would be to browse the commits on sourceforge. ​ I find it cumbersome, however.// //An alternative would be to browse the commits on sourceforge. ​ I find it cumbersome, however.//
  
-Update the release notes to reflect the commits since the last release.+  * Update the CHANGELOG ​to reflect the commits since the last release.  Wrap to 72 columns for email. 
 +  * Copy the latest version to a new page [[:​start#​release_notes|on the wiki]].
  
-  http://​www.rosegardenmusic.com/​wiki/​dev:​next_version+===== Update appdata =====
  
-When finished, move the release notes from the "​Upcoming Release"​ page on the wiki to an official versioned release notes page on the wiki.+Add release notes for the new release ​to the appdata file:
  
-//Consider including the release notes within the tarball in the future Maybe just accumulate them in a single file What do other projects do?  Changelog!//​+  data/appdata/rosegarden.appdata.xml
  
 +Validate with appdatacli:
 +
 +  appstreamcli validate data/​appdata/​rosegarden.appdata.xml
  
 ===== Update the README ===== ===== Update the README =====
Line 67: Line 71:
 Update anything else that seems like it needs updating. Update anything else that seems like it needs updating.
  
 +===== Update AboutDialog.cpp =====
 +
 +Update copyright year as needed.
  
 ===== Update data.qrc ===== ===== Update data.qrc =====
  
-Run "​scripts/​rebuild-qrc"​ 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.
  
  
Line 105: Line 112:
 //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.// //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 ====
 +
 +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: 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:
Line 116: Line 127:
  
 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.
 +
 +=== 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. Any errors related to a "​wallet"​ can safely be ignored and the wallet UI can safely be closed via the "​cancel"​ button.
Line 127: Line 144:
   - Create new version directory on sf   - Create new version directory on sf
   - Upload the tarball to sf   - Upload the tarball to sf
-  - Upload the release notes to sf as README.  Wrap to 72 columns for email.+  - 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.  Set "​Download Button:"​ text to "​Rosegarden xx.xx"​.
  
Line 143: Line 160:
   * /​website/​index.shtml (http://​www.rosegardenmusic.com/​)   * /​website/​index.shtml (http://​www.rosegardenmusic.com/​)
     * Update version.     * Update version.
-    * Copy in release notes summary.+    * <del>Copy in release notes summary.</​del>​
     * Update link to release notes on wiki.     * Update link to release notes on wiki.
  
 
 
dev/release_process.1544673230.txt.gz · Last modified: 2018/12/13 04:53 by tedfelix
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki