Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Thu, 9 May 2002 13:09:06 +0200
From: John Marshall <johnm AT falch DOT net>
To: cygwin-apps AT cygwin DOT com
Subject: Re: setup goals
Message-ID: <20020509110906.GA1651@kahikatea.falch.net>
References: <FC169E059D1A0442A04C40F86D9BA7600C5FF7 AT itdomain003 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA7600C5FF7@itdomain003.itdomain.net.au>
User-Agent: Mutt/1.3.27i
Organization: Falch.net

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?

    John