Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 09:29:16 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: About Cygwin announcements Message-ID: <20050908072916.GZ5555@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050908001841 DOT E93A083C9A AT pessard DOT research DOT canon DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050908001841.E93A083C9A@pessard.research.canon.com.au> User-Agent: Mutt/1.4.2i On Sep 8 10:18, Luke Kendall wrote: > 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?). What's different in this approach in relation to having an announcement mailing list archive? Well, except for double bookkeeping. If somebody forgets to announce (and the head maintainers forget to kick this somebody), then the same would happen with the CVS entry, wouldn't it? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/