Re: cvs: php-src(PHP_4) /sapi/continuity CREDITS capi.c config.m4
| From: | Wez Furlong | Date: | Sun, 07 Dec 2003 23:49:44 +0000 |
| Subject: | Re: cvs: php-src(PHP_4) /sapi/continuity CREDITS capi.c config.m4 | ||
| References: | 1 2 3 4 5 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-25065@lists.php.net to get a copy of this message | ||
> And, I see now, 4_3_2 is that branch it looks like.
No, PHP_4_3 is the stable, feature-frozen branch.
> I'm really disappointed that 4 is closed to my module because I think
> people are going to keep using 4 for some time after 5 releases, but,
> I'll get over it.
Nothing is stopping you from maintaining a patch against PHP_4_3.
> 5 current isn't building, which I doubt is unusual. What's the usual
> practice, work off one of the tags (5_0_0b2?) and then commit into
> current?
Work against HEAD; the RM (Release Master) takes care of branching,
and once branched for a release, only bug fixes are merged into that
branch.
> Also, is there any information on this (CVS practices on branches and
> release status) already?
I could have sworn that we used to have a release process
readme in the tree, but don't see it now; if in doubt, ask
on internals@ (actually, searching php-dev@ archives might
have been a good first step too ;-).
--Wez.