On Sat, 23 Mar 2002, Jim Winstead wrote:
> we should either ditch this file, or update it to reflect the current
> process. (i'd almost prefer we just replace it with an entirely new
> document, perhaps based on derick's email[1], so we can have the
> document not be GPL'd, which is just silly.)
>
> one way i'd amend the process, relating to the use of cvs tags:
>
> the current 4.2.0 (4.2.x?) branch was tagged as 'PHP_4_2_0'. this means
> that the actual 4.2.0 release will need to use some other tag.
Currently releases have a tag with lower case characters (ie php_4_2_0),
while branches have uppercase characters (PHP_4_2_0). I can't say this is
beautiful though :)
>
> the way i'd like to see it done is for the branch tag to look something
> like BRANCH_PHP_4_2 (yes, with 'BRANCH_' in the name. it makes it
> drop-dead easy to tell what is a branch, and what is a release tag) with
> release tags of the form PHP_4_2_0_RC1, PHP_4_2_0, PHP_4_2_1_RC1, etc.
looks like a good idea to me.
>
> i think the whole release process could be tightened up, to boot -- i
> don't see why there needs to be any delay between branching for the
> release and kicking out the first release candidate.
The reason for this was that the QA team (mostly me) was working on the
buildtrackers and testcases to record the RC builds; I agree though that
it shouldn't be necessairy.
> i don't think it
> significantly changes the odds that the first release candidate will be
> the only release candidate (which are near zero, in either case), but i
> think that having a downloadable tarball is always going to attract more
> testers.
But we still don't have enough of them :I
Derick
-----------------------------------------------------------------------
PHP: Scripting the Web - [EMAIL PROTECTED]
All your branches are belong to me!
SRM: Script Running Machine - www.vl-srm.net
-----------------------------------------------------------------------
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
