DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=uQH
	xczqQleY+ydgWEujorQ1aCzAajurLu6JD1hTT1tV/lk7cu8E3pJppFEIWxUwGqrJ
	0lSJcdqhVL7BIytoJ2sL62geSzYxTLX2WZ4V6qMM1+9evgkBatGG9/WN+SSFWRGw
	7dOCtXnYkIz3JUmJbDxn2MTHFAOnsVEx64ZYhFvo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epa.gov>
Subject: does anyone care about package minor version bump announcements?
Date: Thu, 19 Nov 2015 10:13:38 -0500
Lines: 16
Message-ID: <tmor4bp8h0osb27rn2sn4mviph91391247@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lately I find myself feeling quite unmotivated about writing a mostly
boilerplate announcement every time I upload a minor version bump of a
package I maintain.

"stow has been updated from version 2.2.0 to 2.2.2.  You can read the
upstream changelog to see what changed.  stow is blah blah blah"

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.

Andrew


--
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