Return-Path: 
 <cocoon-dev-return-22463-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 41899 invoked by uid 500); 8 Feb 2002 08:40:02 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 41888 invoked from network); 8 Feb 2002 08:40:02 -0000
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Crossley <crossley@indexgeo.com.au>
Reply-To: crossley@indexgeo.com.au
To: cocoon-dev@xml.apache.org
Subject: high-level entries for changes.xml (was: [Announcement] Apache Cocoon
 2.0.1 Release)
Date: Fri, 8 Feb 2002 19:37:13 +1100
X-Mailer: KMail [version 1.2]
References: <GMEBIBHGAOFGJCDPJANDMEFEDJAA.cziegeler@s-und-n.de>
In-Reply-To: <GMEBIBHGAOFGJCDPJANDMEFEDJAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
Message-Id: <02020819371303.01301@igacer>
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Carsten Ziegeler wrote:
> Stefano Mazzocchi wrote:
> > Edd Dumbill wrote:
> > > Carsten Ziegeler wrote:
> > > > Apache Cocoon 2.0.1 Released
> > > > ----------------------------
> > > 
> > > I've given this a mention on the XMLhack newswire.  If the release note
> > > had included major diffs between 2.0.1 and 2.0.0 I could have made a
> > > bigger article out of it -- if you're able to, it would be good to see
> > > more detailed announcements.  I just didn't have the time/context to
> > > figure out what was significant and what wasn't from the ChangeLog.
> > 
> > Very good point, Edd.
> > 
> > We'll make sure that next announcements will be more detailed and more
> > informative both to users and to the press people that help us spread
> > the word.
> > 
> > Thanks for your 'bug report' :)
> 
> I fixed this 'bug' after the 2.0.1 release as soon as I got aware of it.
> So our next announcements are more verbose. Promised.
> 
> Carsten

We could tweak the DTD changes-v1?.dtd to provide a
high-level announcement action in changes.xml which would
then get extracted at Announcement time. One easy way
would be to provide an additional value for the "type" attribute
of the <action> element.
 types "add|remove|update|fix" ... |announce

In that way actions can be described in detail as per normal.
If the change or new feature is worthy of mention in the
Announcement, then we add another <action> entry to provide
the specific announcment text.

--David Crossley

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org