[
https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567525#action_12567525
]
Doron Cohen commented on LUCENE-1157:
-------------------------------------
So there will be:
http://svn.apache.org/repos/asf/lucene/java/site/docs/changes/Changes_2_1_0.html
http://svn.apache.org/repos/asf/lucene/java/site/docs/changes/Changes_2_2_0.html
http://svn.apache.org/repos/asf/lucene/java/site/docs/changes/Changes_2_3_0.html
These will be created once, now, for previous releases, and for future releases
as part of the (to be updated) release steps.
I like this except for one thing: what it means for fixing a release branch.
Today fixing a release branch requires to also update CHANGES.txt.
>From now on it would require to generate Changes.html and check it in.
My concern is that people would forget to update this file, and we will have a
nice html view of changes but it would not be up-to-date.
Up to today I saw branch updates only as part of last minute fixes of the
to-become-a-new- release.
But it is not impossible that critical fixes will be merged in the future into
an existing releases.
"Release To Do" can be extended with the required steps for fixing/updating a
release branch.
Being a rare practice this might be enough...?
> Formatable changes log (CHANGES.txt is easy to edit but not so friendly to
> read by Lucene users)
> -------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1157
> URL: https://issues.apache.org/jira/browse/LUCENE-1157
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Website
> Reporter: Doron Cohen
> Assignee: Doron Cohen
> Fix For: 2.4
>
> Attachments: lucene-1157-take2.patch, lucene-1157-take3.patch,
> lucene-1157.patch
>
>
> Background in http://www.nabble.com/formatable-changes-log-tt15078749.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
