Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 8 Sep 2005 10:18:41 +1000 (EST)
From:	Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
Subject:	About Cygwin announcements
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Message-Id:	<20050908001841.E93A083C9A@pessard.research.canon.com.au>

Despite reading all the Cygwin announcement emails assiduously, I'm
occasionally surprised to learn of significant improvements that
weren't mentioned in the announcements.

No one has a perfect memory, so I can easily see how it'd be easy to
overlook mentioning some great new feature, in an announcement.

Can anyone think of a way to make it easier to produce announcement
emails that faithfully reveal all the great work that's gone on?

What about storing a changelog file in cvs for each package, and
encouraging people to update the changelog (say, by altering the
default text that CVS shows you when you commit a change?).

Just thinking out loud ...

luke


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -