Re: Re: Tagging releases

Johannes Schlüter wrote: > On Fri, 2009-07-24 at 15:00 -0400, Gwynne Raskind wrote: >> And I'm happy to announce that this is now fixed; creation of tags is >> now allowed. This comes alongside a bit of an overhaul of the entire >> set of hook scripts. See http://news.php.net/php.cvs/59765 >> if you're >> desperately curious :). > > I'm not that curious that I read the read the code but curious enough to > ask: What happens if one figures out that a (freshly set) tag is wrong > (maybe missing a file or something) and a re-tag is required? May I > delete the tag and then set it again? - This should be mentioned in the > README.RELEASE_PROCESS, maybe (Yes, the need should never be there but > well, you know ;-)) Note: removing pear-dev from CC: Hi, 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. Greg