Hi, On Fri, 2009-07-24 at 16:14 -0500, Greg Beaver wrote: > I think it would be better to make the release process like this, with > 5.3.1RC1 as an example: > > (1) svn copy http://svn.php.net/repository/php/php-src/branches/PHP_5_3 > http://svn.php.net/repository/php/php-src/branches/php_5_3_1RC1 > > (2) do the release building in the branch and when the release is out on > php.net > > (3) make the tag by moving the branch: svn mv > http://svn.php.net/repository/php/php-src/branches/php_5_3_1RC1 > http://svn.php.net/repository/php/php-src/tags/php_5_3_1RC1 > > also possible would be to svn copy it and wait 2-3 days before svn rm to > allow easy fixing of problems with the tag. > > This would also make it possible to develop continuously on PHP_5_3 > without fear of futzing up a release.
I don't have enough experience with svn and I think this branch should then be merged back (svn merge) into the main branch so that the release can be seen when browsing history - and no last minute change is being lost. Independently there still might be a case where a tag is identified as being wrong before the release was done and therefore might need a change (again, shouldn't happen and so on ... and once it's released the tag shouldn't be changed anymore at all) johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
