Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77801 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73982 invoked from network); 7 Oct 2014 14:08:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Oct 2014 14:08:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.173 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.173 mail-qc0-f173.google.com Received: from [209.85.216.173] ([209.85.216.173:58066] helo=mail-qc0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/89-30869-ED3F3345 for ; Tue, 07 Oct 2014 10:08:30 -0400 Received: by mail-qc0-f173.google.com with SMTP id x13so5762792qcv.32 for ; Tue, 07 Oct 2014 07:08:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=s680cSzLNRoAH3AMW1g8hOyka0Sq240qx3TejxzQ+nk=; b=X6gVAVbAecigulTEkjeq5uF+0vhKMNVTs6zdMxrI4cLu9Fxbn7hSa/Tlj9CDzUmkOc 970akqkk0lQCtFSzUj/mIeOVaS8upgbr+LFrpLkKCmNXIbqMQKkxvLpO+i381DMWBeyM g0C7CUdJLY2HdM/RQbMKBy0SETpM0FkajArKlb0PHDMZdBVn1V+Hn5TY9OAuJwGw1pOd ch7e3xpinrNwD8jHprVnVyLCCK0/HX0x/bVP6XmVEXnh5rN7/q437+t6kluMD8cozXI3 APCSzoBlR+l8cjUANNWSn6YRjWe57/nGfRObVnFmG8RXoBAUCKrwI74rYxxIdKrm0BZ9 fCUA== MIME-Version: 1.0 X-Received: by 10.140.104.13 with SMTP id z13mr18481592qge.81.1412690907839; Tue, 07 Oct 2014 07:08:27 -0700 (PDT) Received: by 10.140.107.130 with HTTP; Tue, 7 Oct 2014 07:08:27 -0700 (PDT) Date: Tue, 7 Oct 2014 16:08:27 +0200 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary=001a1134f080bd4f510504d5bb51 Subject: schedule for 5.6.2 From: tyra3l@gmail.com (Ferenc Kovacs) --001a1134f080bd4f510504d5bb51 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 the 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! --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a1134f080bd4f510504d5bb51--