Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89747
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
To: "'Ferenc Kovacs'" <tyrael@php.net>,
	"'Julien Pauli'" <jpauli@php.net>
Cc: "'Remi Collet'" <remi@php.net>,
	"'PHP Internals'" <internals@lists.php.net>,
	"'Anatol Belsky'" <ab@php.net>,
	"'Stanislav Malyshev'" <stas@php.net>
References: <000c01d12fa0$384b8040$a8e280c0$@belski.net>	<CAMUwpuTFc1FhGSqFczeeOU=H=6F5URhEnmm78uiRjWG1-NT89g@mail.gmail.com>	<082001d131ac$ab522b80$01f68280$@belski.net>	<5666C73B.1050407@php.net>	<CAMUwpuQTfja0bWFDuO3SVHm6=UE4jX7H+oWQ4yDH0AD1GMEw8Q@mail.gmail.com> <CAH-PCH7khdTDZ57wEmTSsZcy0Y_XEUTR_ZViqVSkVzwjRmZkQg@mail.gmail.com>
In-Reply-To: <CAH-PCH7khdTDZ57wEmTSsZcy0Y_XEUTR_ZViqVSkVzwjRmZkQg@mail.gmail.com>
Date: Tue, 8 Dec 2015 15:02:47 +0100
Message-ID: <086601d131c1$210ec400$632c4c00$@belski.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQLQUUADa5bV4IS9/QID+zXMY+qBmwHKzS9nAorb3ecCF2RFJwHSuhMUAdQHQHeccjzQkA==
Content-Language: en-us
Subject: RE: [PHP-DEV] Re: PHP 7.0.1 scheduling
From: anatol.php@belski.net ("Anatol Belski")

Hi Ferenc,

> -----Original Message-----
> From: tyra3l@gmail.com [mailto:tyra3l@gmail.com] On Behalf Of Ferenc
> Kovacs
> Sent: Tuesday, December 8, 2015 2:41 PM
> To: Julien Pauli <jpauli@php.net>
> Cc: Remi Collet <remi@php.net>; PHP Internals =
<internals@lists.php.net>;
> Anatol Belsky <ab@php.net>; Stanislav Malyshev <stas@php.net>
> Subject: Re: [PHP-DEV] Re: PHP 7.0.1 scheduling
>=20
> On Tue, Dec 8, 2015 at 1:26 PM, Julien Pauli <jpauli@php.net> wrote:
>=20
> > On Tue, Dec 8, 2015 at 1:04 PM, Remi Collet <remi@php.net> wrote:
> > > Le 08/12/2015 12:36, Anatol Belski a =C3=A9crit :
> > >> Yeah, particularly our release schedule collides with many =
holidays
> > this year. For a security release a holiday time is obviously very =
bad.
> > >
> > > +1
> > >
> > > Our Release Process state:
> > >
> > >         " At least one release per month, more at wish "
> > >
> > > Perhaps we should consider new release on
> > >
> > >         " 1st thursday of the month "
> > >
> > > (It seems every year, Christmas is end of month ;)
> >
> >
> > Yep, end of year has always collided with our release cycle.
> >
> > Perhaps we should change this latter as proposed by Remi ?
> >
> >
> > Also, we had another idea.
> >
> > Why not use RC2 as a chance for some security patches to get tested =
?
> > If we have a RC2 (which is not bad IMO, we have a time slice here at
> > end of 2015 that enables us to release an RC2) , we then could merge
> > into this one some well-selected security patches, f.e, some that =
are
> > *low* classified , aka that can't get trigerred remotely by user
> > payload.
> >
> > What you think ?
> >
> > CCing Stas as well, as he got many experience in security.
> >
> >
> > Julien.P
> >
>=20
> we are just iterating by two weeks which makes the monthly release not
> monthly but every 28 days, which is fine but that also means that =
sometimes the
> release dates are not always at the same date on each month (stating =
the
> obvious).
> I think that there is no better alternative, we just have to handle =
the exceptional
> cases.
> As we seem to have security fixes (and unfortunatelly at least one of =
those were
> directly pushed by laruance so now it is public information) maybe we =
should
> release it one week earlier (cutting the RC period one week shorter) =
instead of
> delaying it until january?
Yeah, that works for 7.0 alone in any case. If it's about 7.0.1 only, it =
were

- 7.0.1RC1 on 10th December
- 7.0.1 final on 17th December
- 7.0.2RC1 on 24th or 31st
- 7.0.2 final next year together with 5.5.31 and 5.6.17

Probably it could make sense, 7.0.1 in any case on 17th then - what was =
disclosed was only one patch and relevant for 7.0 only. 17th is also =
holiday free, hopefully :) If PHP 5 branches could not be so far, we =
should indeed get 7.0.1 out this year, and we would sync 5 and 7 release =
dates starting with 7.0.2 and next year. How does it sound?

Regards

Anatol