| | 60 | |
| | 61 | |
| | 62 | == Release process in a branch == |
| | 63 | |
| | 64 | In order to allow a few days of stabilization of Padre and to allow the translators to catch up while |
| | 65 | allowing everyone else to freely work on the main trunk we can start releasing from a branch. Trying to capture |
| | 66 | the process here. |
| | 67 | |
| | 68 | * A few (2 ?) days before the planned release date the release manager creates a copy: |
| | 69 | * run perltidy on the trunk |
| | 70 | * svn cp http://svn.perlide.org/padre/trunk/Padre http://svn.perlide.org/padre/branches/Padre-X.XX (replace X.XX with the future version number) |
| | 71 | * Anyone who wants to work on the release branch can |
| | 72 | * cd trunk/Padre |
| | 73 | * svn switch http://svn.perlide.org/padre/branches/Padre-X.XX . |
| | 74 | * then every commit will go to the branch while the plugins are still from trunk |
| | 75 | * the release can be done here but probably it is better NOT to run the perl tidy on the branch as it will make merging very difficult |
| | 76 | * do the regular release process as above |
| | 77 | * when finished merge the branch back to trunk: |
| | 78 | * svn switch http://svn.perlide.org/padre/trunk/Padre . |
| | 79 | * svn log --stop-on-copy http://svn.perlide.org/padre/branches/Padre-X.XX |
| | 80 | * Take the FIRST and LAST revision number from that log |
| | 81 | * svn merge -rFIRST:LAST http://svn.perlide.org/padre/branches/Padre-X.XX/ . |
| | 82 | * svn commit -m'merge -rFIRST:LAST http://svn.perlide.org/padre/branches/Padre-X.XX/' |
| | 83 | * now you can remove the release branch: |
| | 84 | * svn rm http://svn.perlide.org/padre/branches/Padre-X.XX/ |
| | 85 | |
| | 86 | |
