public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com, cygwin-developers@cygwin.com
Subject: Re: Updated: 1.7.0-34 (...and a plea)
Date: Mon, 08 Dec 2008 18:01:00 -0000	[thread overview]
Message-ID: <20081208180050.GA27323@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20081208171615.GB12905@calimero.vinschen.de>

On Mon, Dec 08, 2008 at 06:16:15PM +0100, Corinna Vinschen wrote:
>On Dec  8 12:01, Christopher Faylor wrote:
>> On Fri, Dec 05, 2008 at 12:07:33PM +0100, Corinna Vinschen wrote:
>> >Btw., does anything speak against opening Cygwin up for public testing
>> >on the Cygwin main list?
>> 
>> I think it is a good idea but I'd like to start tracking 1.7.x like a
>> normal release and increasing the x with each new release.  That will
>> allow us to figure out problems from source code more easily.
>
>I thought we stick to 1.7.0 until we create the first actual release in
>which case we bump the version to 1.7.1.  After that we bump every time
>again, as in earlier releases.

Does it really matter?  I've never been a big fan of tracking versions
outside of CVS.  There is a rationale for tracking the version bump
since we can figure out what 1.7.1 relates to but not 1.7.0-39.  We
could CVS tag each release with a '-39' but we currently only do that
sporadically as needed.

>> I don't think there is any reason for people to start rebuilding their
>> packages now either.  That will happen over time when 1.7.x is finally
>> adopted.
>
>Btw., when 1.7 is adopted, we will have to make release-2 an independent
>directory again, right?  Otherwise we will still pull in new 1.5 packages
>which will have inferior features.

I think that when 1.7 is adopted

release-2 -> release
release -> release-deprecated

and we make setup.exe changes to accommodate that.

cgf

  reply	other threads:[~2008-12-08 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 12:44 Updated: 1.7.0-33 (New method to logon without password ... with password) Corinna Vinschen
2008-12-05 11:07 ` Updated: 1.7.0-34 (...and a plea) Corinna Vinschen
2008-12-05 13:06   ` Chris Sutcliffe
2008-12-05 14:07     ` Corinna Vinschen
2008-12-05 17:00     ` Charles Wilson
2008-12-05 13:59   ` Eric Blake
2008-12-05 14:09     ` Corinna Vinschen
2008-12-08 17:02   ` Christopher Faylor
2008-12-08 17:15     ` Corinna Vinschen
2008-12-08 18:01       ` Christopher Faylor [this message]
2008-12-08 18:15         ` Corinna Vinschen
2008-12-08 19:56           ` Christopher Faylor
2008-12-09 10:19             ` Corinna Vinschen
2008-12-09 13:48               ` Corinna Vinschen
2008-12-09 14:47                 ` Brian Dessent
2008-12-09 14:59                   ` Corinna Vinschen
2008-12-09 15:02                   ` Christopher Faylor

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=20081208180050.GA27323@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=cygwin-developers@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).