Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Mon, 22 May 2000 17:56:02 -0400 Message-Id: <200005222156.RAA31137@envy.delorie.com> From: DJ Delorie To: earnie_boyd AT yahoo DOT com CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <20000522214209.15985.qmail@web120.yahoomail.com> (message from Earnie Boyd on Mon, 22 May 2000 14:42:09 -0700 (PDT)) Subject: Re: Next net release will be 1.1.3 References: <20000522214209 DOT 15985 DOT qmail AT web120 DOT yahoomail DOT com> > I don't think this is a big deal. However, this makes the next > major net release need to be 1.2.1, which isn't a big deal either > it's just semantics. Except that net releases are never "supported, official" releases. My original intent was that *..* be reserved for net releases, and *..* be reserved for Cygnus's CD-ROM releases. Thus, net releases will be 1.1.* until the next CD-ROM release, which would be 1.2.0, then net releases become 1.3.*. Example, in chronological order: 1.0.0 initial CD-ROM release 1.1.0 initial net release 1.1.1 new net release 1.1.2 new net release 1.0.1 CD-ROM update (patch kit?) 1.1.3 new net release 1.2.0 new CD-ROM release 1.3.0 new net release 1.3.1 new net release 1.3.2 new net release 1.2.1 CD-ROM update (patch kit?) 1.3.3 new net release