Re: PHP 5
| From: | Tomas V.V.Cox | Date: | Sun, 10 Feb 2002 18:44:31 +0000 |
| Subject: | Re: PHP 5 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4569@lists.php.net to get a copy of this message | ||
Wolfram Kriesing wrote:
>
> On Sunday 10 February 2002 18:03, Martin Jansen wrote:
> > On Sun, 10 Feb 2002 17:26:35 +0100, Jan Lehnardt wrote:
> > >On Sun, 10 Feb 2002 17:20:35 +0100
> > >
> > >Wolfram Kriesing <lists@kriesing.de> wrote:
> > >> if we go for a 2-repository solution, how much extra work does
> > >> it mean? does every bug have to be fixed twice? do you have to
> > >> check in changes in 2 repositories?
> > >
> > >yes, IF, then we'll see some MFP1 (Merged from Pear 1) messages,
> > > and vice versa, like it works with ZendEngine 1 and 2.
> >
> > To me that sounds like a little nightmare.
>
> yep,
> i also think that it wont work everytime. since we are all human and
> may forget a fix some time or copy/paste wrongly:-)
> and this would also mean to test twice, everytime....
>
> is by 2 repositories really meant to have 2 seperate CVS repositories
> or do we only branch?
> is meant to set a tag over all files when we start the PHP5
> compatibility conversion and from there on php4 fixes need to be
> branched?
>
All the files would go to a PHP 4 branch and all the work will be done
in the main branch as today. We would "touch" the PHP 4 branch only for
fixing the bug reports that affects this branch. I'd vote this way,
yeah.
For the pear installer that's no problem. Packages can be built from any
branch and the new packages should set the correct dependency in
package.xml (<dep type="php" rel="ge" version="5" />) if they
rely in
features of the new version.
My only fright is to deal with bugs in PHP 5, I don't really think that
all the things in this new release will work from the first moment
(remember PHP 4?).
Tomas V.V.Cox