lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1157) Formatable changes log (CHANGES.txt is easy to edit but not so friendly to read by Lucene users)
Date Tue, 05 Feb 2008 22:29:08 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565911#action_12565911
] 

Doron Cohen commented on LUCENE-1157:
-------------------------------------

{quote}
I worry that the nightly build documentation is too prominent. A search for "indexwriter api"
on Google or Yahoo! returns nightly documentation before released documentation.
{quote}
Yes.. just tried that.

{quote}
... trying to promote the nightly outside the developer community, which is wrong.
{quote}
I agree. Can this be avoided by robots,txt on hudson?

{quote}
I believe that Doron's intent is to link to the HTML version of the non-released trunk version
of CHANGES.txt from the main web page (please correct me if I'm wrong, Doron)
{quote}
Well I'm not sure where they should be copied to - just want to make the changes accessible.
Perhaps there's no need to copy the changes folder at all (see below).

{quote}
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. 
{quote}
CHANGES.txt is already accessible from "Lucene News" in the main site.
I think it makes sense to generate (once) Changes.html for 2.3 and add it to 2.3 branch and
modify the main site to link to that file.
Also, I think the 2.3 branch docs should link to this file.
(I was planning to get to discuss this later.)

{quote}
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.
{quote}
Only the changes directory is to be copied,
Nightly documentation is copied already today from hudson to  l.a.o/java/docs/nightly.
Doug, are you concerned with current practice, or just with additionally copying the changes
folder?
if the latter. I think it is possible to link/redirect to Changes.html that is generated by
the nightly build on hudson, the same as seems to be done for the javadocs links?


> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message