We need to do some thinking about this 4.1 business, before we actually do
anything. Please don't branch anything at this point - we've had a fairly
bad experience with premature branching with PHP 3.1.
We need to get a clear understanding of what's going to be the main changes
in PHP 4.1, and then shift 99% of the development to it. We've been
discussing this in the group@ forum, and should now move the discussion
here. Generally, the main differences we came up with so far are (as per
Stig):
- Move most of the non-popular extensions out of the release and into PEAR
(requires lots of PEAR work to be made)
- Always build the CGI
- No language-level (i.e. Zend Engine) changes scheduled for this release
at this time
In my opinion, we shouldn't do anything on the repository level until the
new PEAR services are in place. If we do, we're going to shoot ourselves
in the foot - we won't be able to release 4.1, and we won't really have an
updated CVS to release 4.0.x from. It's probably premature to branch at
this time.
In my opinion #2, the changes you mentioned aren't necessarily something
that belongs in 4.1 - they can easily find themselves in 4.0 (you can add
the new XSLT stuff under a different extension, for instance). That's just
my opinion though - you can wait :)
Zeev
At 05:10 14/4/2001, Sterling Hughes wrote:
>On Sat, 14 Apr 2001, Sebastian Bergmann wrote:
>
> > Stig Bakken wrote:
> > > Log:
> > > here's a preliminary list of stuff for 4.1
> >
> > Is there any timeframe for when PHP 4.1.0 will be released?
> >
>
> I don't know, but I'd like to start a branch for the 4.1.0 code in a
> week or so (or sooner, that's just when I'll have a use for it). I've
> got a bunch of stuff to put in, a new XSLT extension (syntax *will*
> change, but speed, stability and memory usage are greatly improved, as
> well as allowing multiple XSLT backends, initial support for
> Sablotron and libxslt). I'd also like to put the ADT stuff in 4.1
> (nearing completion, still have to work up a good proposal). There are
> also some changes in cURL which don't really change the API but would
> be good to announce along with 4.1 (persistent connections)... That's
> just my stuff (I think I have a bit more for 4.1 too :)...
>
> I have a feeling from the todo that other people have a bunch of
> patches or things "todo" for 4.1 as well. Therefore I think setting up
> a branch at this time or pretty soon would be a good idea. That way we
> can start preparing for and stabilizing 4.1.
>
> -Sterling
>
>
>--
>PHP Development Mailing List <http://www.php.net/>
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
Zeev Suraski <[EMAIL PROTECTED]>
CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
