public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add a command to make a test release
Date: Thu, 05 Oct 2017 16:57:00 -0000	[thread overview]
Message-ID: <0f58e59c-2953-b7d2-98d6-de8f2bcd2da1@cornell.edu> (raw)
In-Reply-To: <4nectcp0vd3dvhn5rh5ed0h3difc47jedm@4ax.com>

On 10/5/2017 10:23 AM, Andrew Schulman wrote:
> Sometimes more complicated situations come up. We have one with lftp right now:
> 
> prev: 4.7.7-1
> curr: 4.8.0-1
> test: 4.7.8-1
> 
> This happened because 4.8.0-1 turns out to be broken, and later versions won't
> build in Cygwin yet. So I had to promote 4.7.8-1 to test.

I didn't pay close attention to the lftp bug reports, so what I'm saying 
may be nonsense.  But wouldn't it make more sense to just remove 4.8.0-1 
if it's broken?  You could still make 4.7.8-1 a test version, leaving a 
working 4.7.7-1 as current.

Doing it this way, you wouldn't need anything but the ability to mark a 
release as "test".

Ken

  reply	other threads:[~2017-10-05 16:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 19:51 Jon Turney
2017-10-03 20:01 ` Andrew Schulman
2017-10-03 20:25   ` Achim Gratz
2017-10-05 12:24   ` Jon Turney
2017-10-05 14:23     ` Andrew Schulman
2017-10-05 16:57       ` Ken Brown [this message]
2017-10-05 19:50         ` Andrew Schulman
2017-10-07  7:52           ` Achim Gratz
2017-10-09 19:33             ` Andrew Schulman
2017-10-05 18:16       ` Achim Gratz
2017-10-05 19:33         ` cyg Simple
2017-10-05 18:14     ` Achim Gratz
2017-11-01 19:58 ` Yaakov Selkowitz

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=0f58e59c-2953-b7d2-98d6-de8f2bcd2da1@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@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).