Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Subject: RE: setup goals MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 9 May 2002 21:19:55 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "John Marshall" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g49BK6330962 > -----Original Message----- > From: John Marshall [mailto:johnm AT falch DOT net] > Sent: Thursday, May 09, 2002 9:09 PM > To: cygwin-apps AT cygwin DOT com > Subject: Re: setup goals > > > On Tue, May 07, 2002 at 01:14:35AM +1000, Robert Collins wrote: > > I thought I'd make the setup design and coding and make > goals clear in > > one place - I don't think it's been done recently. > [...] > > Second to last, patches to 'release' branches, such as > setup-200205, > > will only ever be for critical bug fixes, not for UI > enhancements and > > the like. > > To understand this rule, it would be good to know how often > HEAD becomes the production release version. Obviously the > answer is "when it's ready", but can you give an idea of > intention? How much work tends to be bitten off at once? A > couple of months worth, perhaps? Ideally, around once a month. Pragmatically it seems to be ~3-4 months. Rob