Re: PHP 5.6 Process

From: Date: Tue, 15 Oct 2013 12:19:14 +0000
Subject: Re: PHP 5.6 Process
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-69558@lists.php.net to get a copy of this message
On Mon, Oct 14, 2013 at 11:43 PM, David Soria Parra <dsp@php.net> wrote: > Hi Internals > > It's already mid-october and according to our release schedule we have to > release PHP 5.6 in 10 months from now. The past has shown that we need > approx 5 months to stablize a release and go through alpha, beta and RC > stages. Therefore I want to start a discussion on how to move forward > with 5.6, to get a release schedule up as fast as possible so contributors > now when to push their stuff and to vote on RFC's BEFORE the first beta. > > I think over the last years it proved to be good to have the current > RM support a new RM who then takes over after the final release > (e.g. Julien basically does 5.5 alone now, but we worked a lot together > during alpha/beta/RC). Therefore my suggestion is that Julien is going to > help out with 5.6 and then we would need a new RM that can learn from > julien > on how to do things to later be able to do 5.6 on his own. > > Suggestions? > > David > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > I agree with all of the points above. I also think that we could be a bit more pro-active with the already presented RFCs and try to bug the authors or chip in with the implementation so that we don't end up in a situation where every new language construct comes in at the last minute (before or even after the feature freeze). I also think that not that many people familiar with what exactly an RM does, so I think (hope) that the lack of volunteers/candidates for RMing was caused by the fact that most people don't know what are the requirements for being an RM. From my understanding it is a little bit of project management and resolving some disputes whether or not some feature should be approved/rejected(usually you just point to https://wiki.php.net/rfc/releaseprocess RFC), but most of the times it is just following http://git.php.net/?p=php-src.git;a=blob_plain;f=README.RELEASE_PROCESS, so tagging/packaging the release, writing the release announcement, etc. Personally I would propose Nikic to the post, but I would also happy if Johannes or Stas would be a returning RM for the 5.6 release. -- Ferenc Kovács @Tyr43l - http://tyrael.hu

« previous php.internals (#69558) next »