Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77802 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78594 invoked from network); 7 Oct 2014 14:25:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Oct 2014 14:25:24 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.43 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.192.43 mail-qg0-f43.google.com Received: from [209.85.192.43] ([209.85.192.43:50497] helo=mail-qg0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/8A-30869-2D7F3345 for ; Tue, 07 Oct 2014 10:25:22 -0400 Received: by mail-qg0-f43.google.com with SMTP id j107so5485387qga.30 for ; Tue, 07 Oct 2014 07:25:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=j2LPvwvITTizqodqp+aOMHZyGwbCELpeEA/u5/Y/RrY=; b=zS+svG29pw914P5Bmu5YDonFAV2NC1wrWfeA2V6e+wvbjjjbSdQ/2f7p0RCLjz9Oxa yV0FHGE7amdPhDQ3yx3iSHE4iekTMye16bYfyrg1xa3KRfr2ykhPY2eGodkUvImulWiN GtrxLcRga9DFyqR5Q+qWXQyUH84lpEA0ek7UsUBmI9erWNP/pvaCidQst5Noyw4hN3Q3 Gxz0CEIY0WKB3OCEyNhD5HxZyBcN0XkRZCNTNaJQSi8rvZewktItiP74Bl+UIMnjpCj3 EWtsypKp/QzCja6C3jP2Opmkm3r2sQb/kjXQZ6Xz6U25R7oHNsOf0qMM3iMbC060YYYE gtWA== MIME-Version: 1.0 X-Received: by 10.140.104.13 with SMTP id z13mr18626344qge.81.1412691919512; Tue, 07 Oct 2014 07:25:19 -0700 (PDT) Received: by 10.140.107.130 with HTTP; Tue, 7 Oct 2014 07:25:19 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Oct 2014 16:25:19 +0200 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary=001a1134f0800a50de0504d5f8bf Subject: Re: schedule for 5.6.2 From: tyra3l@gmail.com (Ferenc Kovacs) --001a1134f0800a50de0504d5f8bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Oct 7, 2014 at 4:08 PM, Ferenc Kovacs wrote: > Hi, > > currently the 5.6 release schedule is not in sync with 5.4 and 5.5 which > is a bit inconvenient (it is easier to sync between the RMs if they are > targetting the same dates with their release, etc.) plus if we keep that > way, it will be a huge PITA when we have to do co-ordinated release > containing security fixes. > To resolve this we (Stas, Julien and myself) decided to sync the upcoming > releases for the next version, and as 5.4 and 5.5 are already on the same > schedule, the decision was to try to match that with 5.6. > 5.4.34 and 5.5.18 are expected to be released in about two weeks, so here > is the plan: > > - if we have security fixes ready for the next release, 5.6.2 will be > released along with 5.4.34 and 5.5.18 containing nothing but 5.6.1 plus t= he > security fixes and we will follow the same schedule onwards. > - if there are be no security fixes we obviously won't make an identical > release to 5.6.1, so then 5.6.2 will follow the release schedule for 5.4.= 35 > and 5.5.19 and we will follow the same schedule onwards. > > sorry for the inconvenience and the possible confusion, but after this > sync it will be easier for everybody to follow the schedule as there will > be only one schedule to keep in mind! > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu > a little correction: 5.5.18 is expected next week (not in two weeks) and as 5.4 is in security fix mode, 5.4.34 will only happen when we have security fixes to release. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a1134f0800a50de0504d5f8bf--