Re: Final version, RFC release process

From: Date: Wed, 01 Jun 2011 11:07:35 +0000
Subject: Re: Final version, RFC release process
References: 1  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
Hi,

In my opinion a restriction "API compatibility must be kept (internals and userland)" for x.y.z to x.y+1.z is too strict. It just can block some new features forever.

I would suggest to change "API compatibility must be kept" to "API backward compatibility must be kept as much as possible".

Thanks. Dmitry.


On 06/01/2011 02:09 PM, Pierre Joye wrote:

Hi,

Long due but finally sending the final RFC for the release process.

There a couple of changes since the last time, they are all about
making it more transparent or catch the edge cases. We also got new
proposers on board, we are now basically almost all active devs on
board.

URL: https://wiki.php.net/rfc/releaseprocess

In parallel to the current discussions about 5.4's features, let get
this RFC approved and use right away for 5.3 (to define its life time)
and 5.4. That will spare us the issues we had in the past with 5.3,
for example and ensure that we get 5.4 release in a reasonable
timeframe and without endless delays, or features additions.

It is important to keep in mind that this RFC is not written in stone
but it is a good base to begin with. We can always adapt it later, if
necessary.

https://wiki.php.net/rfc/releaseprocess/vote for the votes, pls add
your svn id. Proposers do not need to do it as they are indeed there
as +1 already (I added myself as example)

Cheers,
--
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org

Thread (38 messages)

« previous php.internals (#52649) next »