Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 22 May 2000 17:22:49 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Next net release will be 1.1.3
Message-ID: <20000522172249.A10159@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i

It makes sense to "increment by two" for each net release.  This means
that if someone downloads a snapshot (which will be something like
1.1.2, 1.1.4, etc.) they'll be able to upload to 1.1.3, 1.1.5, etc.

The only slight inconsistency in this plan is that it is the opposite of
the "stable releases are even, beta net releases are odd".  Since it's
likely that few people besides DJ and I are aware of this even/odd
relationship, I'm wondering if this is a big deal.

If so, I guess the next net release will be 1.1.4.

cgf