Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52675 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15945 invoked from network); 1 Jun 2011 13:59:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 13:59:25 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 74.125.82.170 mail-wy0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:48908] helo=mail-wy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/D2-32367-CB546ED4 for ; Wed, 01 Jun 2011 09:59:25 -0400 Received: by wyb34 with SMTP id 34so4655172wyb.29 for ; Wed, 01 Jun 2011 06:59:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SkQ1qPFC2/wIyGrFjhBUpIY2AGcElHWLnKwxS+Ke+i4=; b=wlgB9qnstqAg9QLtEOmzdbjfmgdRksQ0sd1Bhoy44aDv4uYzJ1sRmqgmU0wfjHU7ZV SLmmJE+ZCsjEWEFE9q7fj5HAGxVOilxOP257gGOtTOcbC4jHmXWq5/idkQjaFqSqrB/F x9HO6TmrrFtjXt/I4hp/ly2jsIM2xHAh4gHEU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UInNn9DDFvUqAACIKdUUDiNbDms/HJZVRqd/dB4KgCHaZM4bJjxiuG/tuOoR7S6Y0j g8652w7VknpQluKYpTjTA7FDaOb0DSDXAvPKoe7JnOt7/WEb5ro2a43Zgz39bAYCYmXU GiOjDCstJhFCwnx+Uygaj7rxmb2RuO+CiEZJk= MIME-Version: 1.0 Received: by 10.216.28.200 with SMTP id g50mr1902458wea.92.1306936761507; Wed, 01 Jun 2011 06:59:21 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Wed, 1 Jun 2011 06:59:21 -0700 (PDT) In-Reply-To: References: <1306932263.1952.112.camel@guybrush> Date: Wed, 1 Jun 2011 15:59:21 +0200 Message-ID: To: Ilia Alshanetsky Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= , Derick Rethans , PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] Final version, RFC release process From: pierre.php@gmail.com (Pierre Joye) 2011/6/1 Ilia Alshanetsky : > Pierre, > > Doing a release could be simplified through automation as you've said. > However keeping synchronized patches across frequently incompatible > (non-identical) code bases is much less trivial and requires quite a > bit of work by anyone making the bug fixes. Having >3 branches for bug > fixes makes this very non-trivial and time consuming, which is why > Johannes' proposal is so appealing. I don't think we will ever have >3 releases for bug fixes but maybe 3-4 max with 2-3 in security modes. In this case it is really easy to maintain and release. Random LTS at random point with random life time for releases is not something I want for PHP. It is basically what we have now and PHP users are really not happy about that (and many devs). Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org