Hi Oliver,
to which subsection should we add our entries: "Slide 2.0b1" or "Slide pre 2.0b1"?

Thanks,
Peter 

> -----Original Message-----
> From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 19, 2004 14:49
> To: Slide Developers Mailing List
> Subject: CHANGELOG / WAS Re: 2.0 Release: What is in the pipeline?
> 
> 
> I got the impression the changelog features in Slide are basicly 
> sufficient for what *I* wanted to log. I only added date/author 
> attributes as I consider them essential and a reference to 
> the bugzilla 
> that is generated out of the bugzilla bug id.
> 
> I resurrected changelog.xml which is located at src/doc/changelog.xml 
> and *kindly ask all committers to update it every time they check in 
> something* non-trivial. A short notice on a high level like the ones 
> found in release notes should be just right. The XML is very easy and 
> should be self-explanatory when you look at the other 
> entries. An entry 
> might look like:
> 
>        <add date="January 15, 2004" author="ozeigermann" 
> bugzilla-id="4711">
>               Added new build targets to install Slide into 
> Tomcat 4 and 5
>        </add>
> 
> Oliver
> 
> Oliver Zeigermann wrote:
> 
>  > All this "What has been changed?" and "Where did these 
> fixes go?" really
>  > is a general problem. I know all the information is in the 
> CVS, but is
>  > sometimes hard to find and manage. I would propose to use 
> some sort of
>  > logging where every non-minor change gets recorded. We use 
> a small DTD
>  > and XSLT script that converts log entries done in XML into 
> text/HTML
>  > output and also release notes. There are some other little 
> features like
>  > references to the bugzilla for bug fixes. All the author 
> of a fix/change
>  > would have to do is add a log to the XML file like in weblogs.
>  >
>  > I would like to see this type of logging of changes in Slide 2.0. I
>  > would also merge the rudimentary logging capabilities in 
> Slide with this
>  > one...
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to