Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 88890 invoked by uid 500); 14 Jun 2001 16:18:05 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 88846 invoked from network); 14 Jun 2001 16:17:58 -0000 Message-ID: <3B28E368.3DAFB7D5@apache.org> Date: Thu, 14 Jun 2001 12:16:40 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "cocoon-dev@xml.apache.org" Subject: Automagic Announcement Generation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N I added the automagic announcement generation from the Avalon project. This does require a little care and feeding, though. One thing that was forgotten during the Beta 1 release of Cocoon was to adjust the Change logs so that the last release was permanently marked as: This is something that has been forgotten to be done between every version number for the change log. As a result, it is _very_ difficult to figure out what changes and updates happened when. I propose that we do not use the automatic filtering on the change.xml file, and we hand code the versions for the releases in the file. This will force the average developer to realize (hopefully) that my change is in version 2.0b1-dev (will be 2.0b2). Please, be careful with the change log. It is a good tool if maintained correctly. Also, is our TODO list up to date? --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org