Re: formatable changes log

I switched to maintaining the CHANGES file in YAML format for the solr-ruby library: There is even a unit test to make sure it at least parses properly:

RE: formatable changes log

On 01/26/2008 at 3:00 PM, Steven A Rowe wrote: > On 01/26/2008 at 2:26 PM, Doron Cohen wrote: > > On Jan 26, 2008 6:32 PM, Steven A Rowe <[EMAIL PROTECTED]> wrote: > > > On 01/26/2008 at 8:07 AM, Grant Ingersoll wrote: > > > > On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: > > > > > Here's the

RE: formatable changes log

Hi Doron, On 01/26/2008 at 2:26 PM, Doron Cohen wrote: > On Jan 26, 2008 6:32 PM, Steven A Rowe <[EMAIL PROTECTED]> wrote: > > On 01/26/2008 at 8:07 AM, Grant Ingersoll wrote: > > > On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: > > > > Here's the Perl script I wrote to produce the above: > >

Re: formatable changes log

On Jan 26, 2008 6:32 PM, Steven A Rowe <[EMAIL PROTECTED]> wrote: > On 01/26/2008 at 8:07 AM, Grant Ingersoll wrote: > > On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: > > > Here's the Perl script I wrote to produce the above: > > > > > >

Re: formatable changes log

On Jan 26, 2008, at 11:32 AM, Steven A Rowe wrote: On 01/26/2008 at 8:07 AM, Grant Ingersoll wrote: On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: Here's the Perl script I wrote to produce the above: If we choose this, can you don

RE: formatable changes log

On 01/26/2008 at 8:07 AM, Grant Ingersoll wrote: > On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: > > Here's the Perl script I wrote to produce the above: > > > > > > If we choose this, can you donate it? Yes, I can donate it. I put th

Re: formatable changes log

On Jan 25, 2008, at 11:36 PM, Steven A Rowe wrote: On 01/25/2008 at 2:05 PM, Chris Hostetter wrote: As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining it in a simple HTML file? personally, i'm a fan of simple, plain text files for the CHANGES.txt ... easy to edit, e

Re: formatable changes log

On Jan 26, 2008, at 5:05 AM, Michael McCandless wrote: Steven A Rowe wrote: However, I noticed a problem: in CHANGES.txt under the 2.3.0 release in the "Bug fixes" section, there is a gap in the sequence: Argh! Yet more evidence that I cannot count :) This is the 2nd time I've done th

Re: formatable changes log

On Jan 26, 2008 6:36 AM, Steven A Rowe <[EMAIL PROTECTED]> wrote: > On 01/25/2008 at 2:05 PM, Chris Hostetter wrote: > > > As it is becoming hard to browse/navigate CHANGES.txt, how about > > > maintaining it in a simple HTML file? > > > > personally, i'm a fan of simple, plain text files for the

Re: formatable changes log

Steven A Rowe wrote: However, I noticed a problem: in CHANGES.txt under the 2.3.0 release in the "Bug fixes" section, there is a gap in the sequence: Argh! Yet more evidence that I cannot count :) This is the 2nd time I've done that! But my script only notices that it's a numbered lis

RE: formatable changes log

On 01/25/2008 at 2:05 PM, Chris Hostetter wrote: > > As it is becoming hard to browse/navigate CHANGES.txt, how about > > maintaining it in a simple HTML file? > > personally, i'm a fan of simple, plain text files for the > CHANGES.txt ... easy to edit, easy to read. I don't know about easy to re

Re: formatable changes log

: - Need to define all developers/committers in front and assign each an ID, : and use this ID when referring to them. I guess we can ignore this practice ... : Person2). And BTW, AFAICT for now it does not support that P1 via P2 concept : (though that can be requested as a new feature).

Re: formatable changes log

On Jan 26, 2008 2:28 AM, Doron Cohen <[EMAIL PROTECTED]> wrote: > and with a very long file the ability to fold sections is missing > Actually the pdf version gives folding and so easier navigation.

Re: formatable changes log

On Jan 25, 2008 1:28 PM, Doron Cohen <[EMAIL PROTECTED]> wrote: > I'll check it, thanks Michael. > > On Jan 25, 2008 3:03 AM, Michael Busch <[EMAIL PROTECTED]> wrote: > > > Forrest has a plugin called projectInfo that can generate a list of > > changes and an RSS feed from a status.xml file: > > >

Re: formatable changes log

On Jan 25, 2008 9:05 PM, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > : As it is becoming hard to browse/navigate CHANGES.txt, how about > maintaining > : it in a simple HTML file? > > personally, i'm a fan of simple, plain text files for the CHANGES.txt ... > easy to edit, easy to read. I agr

Re: formatable changes log

: As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining : it in a simple HTML file? personally, i'm a fan of simple, plain text files for the CHANGES.txt ... easy to edit, easy to read. that said: if people want to start using a more structured changelog file (xml/html/w

Re: formatable changes log

Doron Cohen wrote: As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining it in a simple HTML file? Requirements are: - fancier formatting where adequate. - collapse/expand by release/subject - easy to maintain... Here is an example, containing the current (new) trunk and

Re: formatable changes log

I'll check it, thanks Michael. On Jan 25, 2008 3:03 AM, Michael Busch <[EMAIL PROTECTED]> wrote: > Forrest has a plugin called projectInfo that can generate a list of > changes and an RSS feed from a status.xml file: > > > http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugi

Re: formatable changes log

+1 I think readability/visibility of the CHANGES, both in CHANGES.txt and also in release announcements, news items, is important for "enticing" people to upgrade... Mike Doron Cohen wrote: As it is becoming hard to browse/navigate CHANGES.txt, how about maintaining it in a simple HTM

Re: formatable changes log

Forrest has a plugin called projectInfo that can generate a list of changes and an RSS feed from a status.xml file: http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/index.html Maybe we should use that? -Michael Doron Cohen wrote: > As it is becoming