Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76704 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91734 invoked from network); 19 Aug 2014 12:54:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Aug 2014 12:54:47 -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.192.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.192.49 mail-qg0-f49.google.com Received: from [209.85.192.49] ([209.85.192.49:35043] helo=mail-qg0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D5/D1-16275-51943F35 for ; Tue, 19 Aug 2014 08:54:47 -0400 Received: by mail-qg0-f49.google.com with SMTP id j107so5834503qga.8 for ; Tue, 19 Aug 2014 05:54:43 -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 :cc:content-type; bh=vNYOhL2vGsxGuHqchE2sfMNHYKhznHD0hb4lfsJXGLo=; b=gSWFbcpA3crE7DNHjJKmDhiwjKJU3OxI2AJZvJn+5hSKZWX7kx2TkkiWzSLdVT+ieK Vbu/BZPd0e+FCz7zjmMszg6GbFUjl64JEPNHbAJKpEZWLqNNQCNEt5qVzqto3VuqLy9N fAn5ct3BPE97Gw/9bAoiZvaGlIwV+Ve8JIxQLcrwrUXaXriphmHOSpSROc2H3HVz943U +qPD8PBDLKBN4/mTnUyuujaqkRscSRhYV5SV1e9o00Lno2oIq0nlgIKKsGvr0xDqaxyg 12SvjyWvekZPWvlNSN6KekFIKIIiS5gA3XR8wBYk4kmQjmpIMgaUz4wwhrWyDSJWIIxd 0Kyg== MIME-Version: 1.0 X-Received: by 10.140.38.169 with SMTP id t38mr62418990qgt.3.1408452882989; Tue, 19 Aug 2014 05:54:42 -0700 (PDT) Received: by 10.140.90.112 with HTTP; Tue, 19 Aug 2014 05:54:42 -0700 (PDT) Received: by 10.140.90.112 with HTTP; Tue, 19 Aug 2014 05:54:42 -0700 (PDT) In-Reply-To: <53F29345.40607@sugarcrm.com> References: <53F29345.40607@sugarcrm.com> Date: Tue, 19 Aug 2014 14:54:42 +0200 Message-ID: To: Stas Malyshev Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a11c12ce6c623cb0500fafd5c Subject: Re: [PHP-DEV] 5.4 security only From: tyra3l@gmail.com (Ferenc Kovacs) --001a11c12ce6c623cb0500fafd5c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014.08.19. 1:59 ezt =C3=ADrta ("Stas Malyshev" ): > > Hi! > > Moving this out of other topics into its own: according to the release > RFC, we should have 5.4 have 2 years of bugfixes & one year of security > fixes. Since 5.4 was released in March 2012, we're already past 2 year > mark. However, we're still have some bugfixes in 5.4, so I'd like to do > this: > > - 5.4.32 is released as planned this week, nothing changes there. > > - 5.4 branch that is to be 5.4.33 will be the last release that has any > non-security bugfixes. We hope that by the time 5.4.33 is out 5.6.0 is > out too, so that would play nice with the "two stable branches, one > security branch" theme. Starting from that release forward, 5.4 would be > purely security fixes only branch. > > - EFFECTIVE IMMEDIATELY, we do not accept new non-security bugfixes into > 5.4 branch unless they are very important ones (and that is only because > people may, in theory, have pending patches and we didn't give advance > notice). Importance would have to be determined somewhat arbitrarily, > but basically if it works without it, then it's not in, if there's > serious doubt if it should be in, it's not in, etc. Security issues, of > course, still allowed in. > > This means if somebody has some pending non-security fixes that have to > be in 5.4, the following two weeks are the last call, provided that the > fixes really must be in 5.4. > > Any objections/suggested modifications to this plan? Nope, I think it is a good plan. --001a11c12ce6c623cb0500fafd5c--