[
https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567458#action_12567458
]
Steven Rowe commented on LUCENE-1157:
-------------------------------------
I think the simplest thing to do would be to put the Changes.html (and .css
files) for the most recent release in the non-versioned {{/site/}} tree:
http://svn.apache.org/repos/asf/lucene/java/site/docs/changes/
It would be updated there as part of the release process. And it could be
linked to from everywhere that now links to CHANGES.txt.
In addition, the per-release documentation (maybe from the Overview page?)
could link to a version of Changes.html that only includes changes up to the
release in question. AFAICT, the per-release documentation is created as part
of the release process.
That leaves the question of whether to include HTML versions of CHANGES.txt for
previous releases - my vote is to do so.
That makes 4 different classes of location for Changes.html:
# Current trunk view, linked from developers' documentation. _(done)_
# Latest release view, linked from the non-versioned site.
# Per-release view for releases going forward - contains changes only up to the
release.
# Per-release view for previous releases - contains changes only up to the
release.
> 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]
