Right, I think we can just generate the file and include it in the
Hudson build and link to it from the dev resource page, right? No
need to copy it to the public website.
On Feb 5, 2008, at 1:30 PM, Doug Cutting (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565843
#action_12565843 ]
Doug Cutting commented on LUCENE-1157:
--------------------------------------
Sure, it makes sense to make changes.txt relatively easy to find,
like the bug database, so that folks can get an idea of what to
expect in upcoming releases. Both should be part of the project's
developer documentation, not the product documentation. I was
mostly responding to the remarks above about copying the nightly
docs to the public website, the motivation for which I don't fully
follow.
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
