From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Cygwin version numbers [Was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1]
Date: Sun, 12 Apr 2015 17:37:00 -0000 [thread overview]
Message-ID: <552A8C03.2070306@dinwoodie.org> (raw)
In-Reply-To: <announce.20150411103504.GD7343@calimero.vinschen.de>
On 11/04/2015 11:35, Corinna Vinschen wrote:
> The version number is 2.0.0-0.1. Yes, we're going full Torvalds with
> the release numbers and bump them to 2.0. In future, bugfix releases
> will bump the last number, new feature releases will bump the middle
> number.
>
> Bugfix? 2.0.1, 2.0.2, ...
> New features? 2.1, 2.2, ...
Does this mean the version number distinction between the GPL and
propriety versions of the Cygwin DLL are disappearing? IIRC it's
currently the case that version 1.<even> indicates a closed-source
license version, and 1.<odd> indicates a GPL-licensed version.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-04-12 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 10:40 [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1 Corinna Vinschen
2015-04-12 17:37 ` Adam Dinwoodie [this message]
2015-04-12 19:11 ` Cygwin version numbers [Was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1] Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552A8C03.2070306@dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).