hi,
The release process RFC (https://wiki.php.net/rfc/releaseprocess)
voting phase is now closed.
The RFC has been approved.
PHP 5.4 will follow it for its development phase and releases.
How we adapt it to PHP 5.3 will be discussed later, especially its EOL.
Cheers,
--
Pierre
@pierrejoye |
On Tue, Jun 21, 2011 at 5:30 AM, Sebastian Bergmann wrote:
> Am 20.06.2011 15:30, schrieb Derick Rethans:
>> 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* wor
Am 20.06.2011 15:30, schrieb Derick Rethans:
> 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.
I agree.
--
Sebastian BergmannCo
On Mon, 2011-06-20 at 09:28 -0500, dukeofgaming wrote:
> On Mon, Jun 20, 2011 at 8:30 AM, Derick Rethans wrote:
> >
> > 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
On Mon, Jun 20, 2011 at 8:30 AM, Derick Rethans wrote:
>
> 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.
>
If its because of the constant merges, it
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 th
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:
h