+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 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 2.3.0 -
http://people.apache.org/~doronc/Changes.html
If people like it I will proceed with the rest of the content.
If not - other suggestions?
- Doron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
