public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: does anyone care about package minor version bump announcements?
Date: Thu, 19 Nov 2015 15:48:00 -0000	[thread overview]
Message-ID: <20151119154843.GB2755@calimero.vinschen.de> (raw)
In-Reply-To: <564DE847.2000502@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

On Nov 19 10:18, cyg Simple wrote:
> On 11/19/2015 10:13 AM, Andrew Schulman wrote:
> > Does anyone care about that?  Lately I don't.  In fact I've skipped sending
> > the last few, and no one seems to have noticed.
> > 
> > Can we leave it to the maintainer's discretion about whether they need to
> > send one of those on every update?  Maybe it already is, and I didn't know.
> > Of course some updates are important or need explanation or a headsup, and
> > then the maintainer should send one.
> 
> My opinion is that every time the package is modified there should be an
> announcement of the new package and what was changed.  Pointing to a
> ChangeLog may be fine but not announcing the change is just wrong.

I agree.  Maybe cygport's new (in testing) "announce" command simplifies
it enough to be not much of a burden?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-19 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 15:14 Andrew Schulman
2015-11-19 15:18 ` cyg Simple
2015-11-19 15:48   ` Corinna Vinschen [this message]
2015-11-19 16:24     ` Nellis, Kenneth
2015-11-19 20:50 ` Andrey Repin

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=20151119154843.GB2755@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).