Re: Re: RFC:PHP Release Cycle
| From: | Rasmus Lerdorf | Date: | Thu, 09 Nov 2000 23:49:27 +0000 |
| Subject: | Re: Re: RFC:PHP Release Cycle | ||
| References: | 1 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-37622@lists.php.net to get a copy of this message | ||
> I have done some work with CVS branches and I don't find them that evil.
> It actually worked quite well for me.
> I am not quite sure we would have problems to create a release branch,
> apply the patch there and merge it into the main branch. I am not convinced
> that it's better for the person to make two separate patches.
I think the patch should go into the main branch first for general
perusal. There may of course be instances where the main branch and the
release branch differ to the extent that the patch won't be the same as
the patch for the release branch, but I have a feeling those instances
won't be too frequent. Once enough people have looked at it and agreed
that the fix is needed in the release branch then the release manager, or
the release team, however we handle it can apply that change to the
release branch.
I have done a lot of CVS work over the years and I have constantly seen
developers have problems trying to merge branches and I don't think we
really need this merge in this case.
-Rasmus