[
https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567416#action_12567416
]
Doron Cohen commented on LUCENE-1157:
-------------------------------------
Yes, I was kinda not sure what to do next - close this (and update changes.txt)
and that's it, or first migrate more links from linking to the raw changes.txt
to link to the fancier changes.html.
The announcement of 2.3 in the main page which now links to 2.3/changes.txt is
one candidate.
The main page of 2.3 docs is another good place for such a link.
Generating the file once is easy enough, and can be done in the future as part
of closing the release.
But where do you link to? I.e. where to put the generated file?
One option is to add it to svn (when the release is closed), and link to it
e.g. like this:
http://svn.apache.org/viewvc/lucene/java/branches/lucene_2_3/Changes.html?view=co
But then future changes to the branch are likely to forget updating this file...
Steven, what do you think of this?
> 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]
