On Wed, 02 Oct 2002, Sascha Schumann wrote:
> Will HEAD become 4.4 immediately after 4.3.0 branches off?
>
> I would expect that some work needs to be done to further
> stabilize the 4.3 branch.
The rule of thumb is that the 4.3 branch is used only for point
releases.
-Andrei
> you mean 4.4? our new rules says to merge only fixes into
> a release branch.
Will HEAD become 4.4 immediately after 4.3.0 branches off?
I would expect that some work needs to be done to further
stabilize the 4.3 branch.
- Sascha
--
PHP Development Mailing List
On Tue, Oct 01, 2002 at 10:38:54PM +0200, Sascha Schumann wrote:
> On Tue, 1 Oct 2002, Andrei Zmievski wrote:
>
> > On Tue, 01 Oct 2002, Sascha Schumann wrote:
> > > Fortunately, I have some spare time and look forward to
> > > purge some of the cruft which has assembled since the CLI
> >
On Tue, 1 Oct 2002, Andrei Zmievski wrote:
> On Tue, 01 Oct 2002, Sascha Schumann wrote:
> > Nope, this is 4.3.1 material.
> >
> > I was about to ask you whether you can branch away the PHP
> > part now and doing the Zend branch later, after the bug is
> > fixed. If not, it is ok
On Tue, 01 Oct 2002, Sascha Schumann wrote:
> Nope, this is 4.3.1 material.
>
> I was about to ask you whether you can branch away the PHP
> part now and doing the Zend branch later, after the bug is
> fixed. If not, it is ok, too.
We were going to branch on Saturday, after Wez
On Tue, 1 Oct 2002, Andrei Zmievski wrote:
> On Tue, 01 Oct 2002, Sascha Schumann wrote:
> > Fortunately, I have some spare time and look forward to
> > purge some of the cruft which has assembled since the CLI
> > support was added. By extending the problem domain, we can
> > si
On Tue, 01 Oct 2002, Sascha Schumann wrote:
> Fortunately, I have some spare time and look forward to
> purge some of the cruft which has assembled since the CLI
> support was added. By extending the problem domain, we can
> simplify and abstract a number of cases in the build sys
> I appreciate your effort on making SAPI part of the build more flexible, but I
> really think that it is unlikely that such a level of flexibility is needed.
> I might be wrong, but I think that a typical user would very seldom require
> more than 1 SAPI + CLI + LIB to be built.
I would arg