Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53402
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Mon, 20 Jun 2011 14:30:55 +0100 (BST)
To: Pierre Joye <pierre.php@gmail.com>
cc: PHP internals <internals@lists.php.net>
In-Reply-To: <BANLkTi=5XWUh-tLbZ6MiJyMvrx4vype_mA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1106201427110.3774@whisky>
References: <BANLkTi=5XWUh-tLbZ6MiJyMvrx4vype_mA@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Can't vote yet, as RFC has "options" (Was: Re: [PHP-DEV] [VOTE]
 release process RFC)
From: derick@php.net (Derick Rethans)

On Mon, 20 Jun 2011, Pierre Joye wrote:

> Hi Internals,
> 
> We have been working on getting this rfc on how to have clear and
> transparent releases process, release cycles and how and which
> features get into a release. The RFC is finally ready for the votes.
> Therefore we call for votes on the release process RFC.
> 
> The RFC can be found here:
> 
> https://wiki.php.net/rfc/releaseprocess
> 
> You can vote here:
> 
> https://wiki.php.net/rfc/releaseprocess/vote

In this RFC, there is still the "options" for both one major and 
multiple major versions at the same time. I don't think you can vote on 
something that is unclear. I therefore voted -1.

I am not generally against this RFC, but this point needs to be 
discussed first IMO. As having 5 active branches at the same time for 
the "multiple major releases" option is *not* workable.

cheers,
Derick