lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen" <cdor...@gmail.com>
Subject Re: formatable changes log
Date Fri, 25 Jan 2008 21:17:50 GMT
On Jan 25, 2008 9:05 PM, Chris Hostetter <hossman_lucene@fucit.org> 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 agree with easy to edit, somewhat less with easy to read/understand..:-)

that said: if people want to start using a more structured changelog file
> (xml/html/whatever) i've got no problem with that ... as long as we have a
> stylesheet that can render it as plaintext.


+1

(even better in my mind would be if we could keep editing in plain text,
> and had some handy scripts to reformat into HTML .. but that's obviously a
> little harder to get perfect and probably not worth the effort.)
>
> The other thing to keep in mind if we're going to start discussing new
> ways to manage change logs is that Jira has automated changelog / release
> notes generation built into it, using the issue summaires...
>
>
> http://issues.apache.org/jira/browse/LUCENE?report=com.atlassian.jira.plugin.system.project:changelog-panel
>
> http://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310110
>
...allthough it's not quite as verbose as our current release notes.


Yes, Changes.txt is definitely needed, more informative.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message