Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50495 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51101 invoked from network); 25 Nov 2010 06:42:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 06:42:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=andi@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=andi@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender) X-PHP-List-Original-Sender: andi@zend.com X-Host-Fingerprint: 63.205.162.117 us-mr1.zend.com Received: from [63.205.162.117] ([63.205.162.117:57209] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/A9-12084-E450EEC4 for ; Thu, 25 Nov 2010 01:42:22 -0500 Received: from us-gw1.zend.com (unknown [192.168.16.15]) by us-mr1.zend.com (Postfix) with ESMTP id 189B02DE23; Wed, 24 Nov 2010 23:30:23 -0800 (PST) Received: from US-EX2.zend.net ([fe80::9c09:d53f:7b4:5880]) by US-EX2.zend.net ([fe80::1d86:6a3c:13cc:f3a7%11]) with mapi; Wed, 24 Nov 2010 22:42:19 -0800 To: Stas Malyshev , Derick Rethans CC: Felipe Pena , internals Thread-Topic: [PHP-DEV] [RFC] Release Process Thread-Index: AQHLiqzj2+bTsIz4aECN+/53nVJ1BJN/XR6AgALZrID//4p8wA== Date: Thu, 25 Nov 2010 06:42:17 +0000 Message-ID: <8757232E56758B42B2EE4F9D2CA019C9142FA2@US-EX2.zend.net> References: <4CEDF661.3090800@sugarcrm.com> In-Reply-To: <4CEDF661.3090800@sugarcrm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: [PHP-DEV] [RFC] Release Process From: andi@zend.com (Andi Gutmans) > -----Original Message----- > From: Stas Malyshev [mailto:smalyshev@sugarcrm.com] > Sent: Wednesday, November 24, 2010 9:39 PM > To: Derick Rethans > Cc: Felipe Pena; internals > Subject: Re: [PHP-DEV] [RFC] Release Process >=20 > Hi! >=20 > >> With the recent chaos in the way we begin and ended releases, we > >> would like to propose a clean way to deal with releases and related > >> decisions: [1] > > > > Really? I think you're blowing this all way out of proportion. > > > > I don't mind a yearly release cycle, as we should get out more releases= . > > I don't mind a monthly release cycle for .z releases. >=20 > I think the idea is not focusing on "yearly" or "monthly" but having some > predictable schedule. Nobody says it should be set in stone, let's be rea= listic > here - if we need to slip a release here and there, we'd do it. But havin= g known > targets is the goal, not having releases "whenever somebody on the list w= akes > up and decides to have a release". I think the project needs to grow up a= bit and > have at least some semblance of release schedule. The mere existence of i= t > written somewhere public would motivate people to adhere to it. I agree with that. More structure and predictability will be very valuable = to the project. We created a lot of structure in Zend Framework and it has = really paid off. Btw, we don't have to look far. Just the change in having people document t= heir suggestions via RFCs already had a substantial impact on this project = both in terms of peer review and having a long lasting trail of what made i= t into a given release. More structure will typically yield in higher quality, more visibility and = therefore more motivation for people to contribute, and I believe also in m= ore deliverables rather than less as people will work towards clear goals += be accepting if they miss them and they need to wait for the next release = train. Andi