General Actions:
Changes for document Release Plan Help
Last modified by Thomas Mortagne on 2013/05/03 20:06
From version 23.5
edited by Jerome Velociter
on 2012/11/16 10:47
on 2012/11/16 10:47
To version 24.1
edited by Jerome Velociter
on 2012/11/16 15:33
on 2012/11/16 15:33
Change comment: There is no comment for this version
Content changes
| ... | ... | @@ -111,6 +111,14 @@ |
| 111 | 111 | Tip: Because the build process is a lenghty one (currently around 2 hours), it is a good idea to use the [[screen linux command>>http://www.rackaid.com/resources/linux-screen-tutorial-and-how-to/]]. This is most helpful in case your Internet connection or electrical power drops. However, it is not in any way mandatory to use screen during the release. |
| 112 | 112 | {{/info}} |
| 113 | 113 | |
| 114 | +{{info}} | |
| 115 | +Tip: running the release script will first ask you for your GPG key passphrase. If you mistype or enter a wrong passphrase, the release will fail to perform. You can test your passphrase locally running the following command : | |
| 116 | + | |
| 117 | +{{code language="bash"}}echo "test" | gpg --no-use-agent -o /dev/null --local-user <KEYID> -as - && echo "Passphrase is correct"{{/code}} | |
| 118 | + | |
| 119 | +If for a reason or another you've made a mistake typing your passphrase in, you will need to delete (locally on the agent machine) the release branch and created tag before you can start over again. | |
| 120 | +{{/info}} | |
| 121 | + | |
| 114 | 114 | == Release Candidate == |
| 115 | 115 | |
| 116 | 116 | In case the version you`ve just build was a ##Release Candidate##, there are 2 extra steps you need to perform, which are to **update the parent version and version properties** on the ##master## branch and to **update the continuous integration jobs** to build the new stable version that you have just created trough the release of a RC version. |