Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29171
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain krug.dk designates 85.214.99.202 as permitted sender)
Message-ID: <463B5492.7040907@krug.dk>
Date: Fri, 04 May 2007 17:43:14 +0200
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC:  internals@lists.php.net
References: <139872287.20070504170744@marcus-boerger.de>
In-Reply-To: <139872287.20070504170744@marcus-boerger.de>
OpenPGP: id=157D0FA8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Starting 5.3
From: edin@krug.dk (Edin Kadribasic)

Hello Marcus,

Adding a new branch is a huge pita for people distributing binary
extension, including our own Windows build and PECL4WIN sites. So
perhaps we should wait with adding a new branch since 5.2 is a really
nice release, the php5 that works very well :)

I think that adding a Phar to the distribution for 5.2.3 is an excellent
idea. I also see no reason to stop adding smaller non-api-breaking
features to 5.2.x and wait until we have a more compelling reason (more
goodies than those listed in points 2-4) to branch out.

Edin


Marcus Boerger wrote:
> Hello internals,
> 
>   i'd like to start 5.3 development from 5.2.2 and have 5.2.* only have
> security relevant changes and no new features whatsoever.
> 
> For the biggest changes i'd like to see the following:
> 1) Adding PECL/Phar as default extension
> 2) Add open_filename debug info to streams
> 3) Add object handler get_debug_info
> 4) Split E_STRICT into E_STRICT and E_DEPRECATED
> 
> a more complete list can be seen here:
> http://oss.backendmedia.com/PhP53
> 
> Besides 1) all mentioned action points require an API change. The first
> point could also be done in 5.2.3.
> 
> As soon as we start with 5.3 development we also need to find a way how
> to keep track of unmerged changes in 5.2/5.3. Right now a lot of stuff
> only happens in 5.2 and eventually gets MFB'ed. An idea is to provide
> an easy way to send commits to bugs.php.net and have them as new category
> "merge required". Maybe we can have the commit script create a link for
> this.
> 
> comments welcome
>   - but please think before writing
>   & only write if you have something to say
> 
> Best regards,
>  Marcus
>