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/07/18 01:33]
tedfelix [Test a Release Build]
dev:release_process [2019/06/13 19:13] (current)
tedfelix [Update the README]
Line 11: Line 11:
 ===== 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: Commit this:
Line 41: Line 41:
  
 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 couple of Release builds and a few sanity checks to make sure nothing is broken.
- 
-  * Qt4 build (-DUSE_QT4=1) 
-  * Qt5 build (-DUSE_QT5=1) 
  
 ===== Update Release Notes ===== ===== Update Release Notes =====
Line 70: Line 67:
 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 =====
Line 84: Line 84:
  
 ===== Commit Changes ===== ===== Commit Changes =====
 +
 +If needed:
  
   svn commit -m "​Updates for version xx.xx"   svn commit -m "​Updates for version xx.xx"
Line 94: Line 96:
   scripts/​make-release-tarball RELEASE   scripts/​make-release-tarball RELEASE
   ​   ​
-Sanity test the tarball. ​ Build and run from it. 
- 
 ==== Tagging the Release ==== ==== Tagging the Release ====
  
Line 108: Line 108:
 //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 119: Line 123:
  
 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. ​ 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 =====
 +
 +Sanity test the tarball. ​ Build and run from it.
  
 ===== Deliver ===== ===== Deliver =====
 
 
dev/release_process.1531870380.txt.gz ยท Last modified: 2018/07/18 01:33 by tedfelix
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki