Changes between Version 21 and Version 22 of Release

Timestamp:

02/15/11 11:54:54 (2 years ago)

Author:

waxhead

Comment:

--

Release

@@ -65 +65 @@
 
 In order to allow a few days of stabilization of Padre and to allow the translators to catch up while 
-allowing everyone else to freely work on the main trunk we can start releasing from a branch. Trying to capture
-the process here.
+allowing everyone else to freely work on the main trunk we can start releasing from a branch. 
 
- * A few (2 ?) days before the planned release date the release manager creates a copy:
+A few (2 or 3) days before the planned release date the release manager creates an svn copy of trunk to branches/release-n.nn.
+
+Prior to creating the copy the following steps are taken:
+
  * run perltidy on the trunk
- * 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)
- * Anyone who wants to work on the release branch can
+ * commit 
+ * Update the Changes file, noting the date of the release being the date you start the branch
+ * commit
+ * set the version from the current development version number to the release version number ( should be even numbered for released odd numbers for development )
+  * Note: there is a script in tools that will update the $VERSION string, however PPI::PowerToys has an awesome ppi_version, use this when you can: ppi_version change old new, ie ppi_version change 0.81 0.82
+ * commit
+ * rebuild the "messages.pot" file, run ../tools/update_pot_file.pl
+ * commit
+
+At this point trunk is ready for you to make the branch:
+ * svn cp http://svn.perlide.org/padre/trunk/Padre http://svn.perlide.org/padre/branches/release-X.XX   (replace X.XX with the future version number)
+
+You have now created the release branch for Padre.
+
+To complete the final tasks on trunk, update the Changes file by "opening" the next version.
+ * Modify Changes, set the next development version number, should be odd and the next release version number, should be even, ie if you have just branched release-0.82, then changes gets updated with:
+
+0.84 TBA
+
+0.83 Dev - not released.
+
+From this point onwards you switch your working copy between the branch and trunk as needed.  To switch between trunk and the branch:
  * cd trunk/Padre
- * svn switch http://svn.perlide.org/padre/branches/Padre-X.XX .
+ * svn switch http://svn.perlide.org/padre/branches/release-X.XX .
  * then every commit will go to the branch while the plugins are still from trunk
  * 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