From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sat, 01 Sep 2018 19:24:00 -0000 [thread overview]
Message-ID: <20180901192356.GN6350@calimero.vinschen.de> (raw)
In-Reply-To: <7684973a80c95141a3b4194aaf33c70b@smtp-cloud8.xs4all.net>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Sep 1 20:08, Houder wrote:
> On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote:
> > I'll fix this and release a 2.11.1 soon, but I still have a question:
> >
> > Why do I push out test releases if nobody cares?
>
> Yes, I know, it is a _hypothetical_question_. You do not really expect
> an answer.
>
> However it was my thought exactly. Nobody? I like to think that those
> that were responsible for patches, have tested their modifications.
>
> I did.
>
> On the other hand, those that will find problems, the people building
> packages, will only do that on "official" releases.
>
> I am almost sure of that :-)
>
> Unless you like creating test releases, releasing only one before you
> push an "official" one, would be more efficient, I imagine.
>
> Yes, you would run the chance that you would have to mend an official
> release several times ... but is that bad?
The idea of test releases is to avoid problem like the one we're discussing
here in official releases. I'd like to get an official release out and
then go on vacation :)
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-01 19:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 1:25 Bryan Phelps
2018-09-01 7:58 ` Andreas Hauptmann
2018-09-01 15:54 ` Corinna Vinschen
2018-09-01 16:42 ` David Allsopp
2018-09-01 19:22 ` Corinna Vinschen
2018-09-02 8:38 ` David Allsopp
2018-09-03 7:39 ` Corinna Vinschen
2018-09-03 19:13 ` Achim Gratz
2018-09-03 20:31 ` Corinna Vinschen
2018-09-01 22:05 ` Andrey Repin
2018-09-02 3:36 ` cyg Simple
2018-09-02 7:32 ` David Allsopp
2018-09-01 18:08 ` Houder
2018-09-01 19:24 ` Corinna Vinschen [this message]
2018-09-01 21:25 ` Houder
2018-09-01 20:08 ` Bryan Phelps
2018-09-01 8:03 ` Marco Atzeri
2018-09-01 8:11 ` Marco Atzeri
2018-09-01 8:31 ` David Allsopp
2018-09-01 9:07 ` Thomas Wolff
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=20180901192356.GN6350@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).