lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] Commented: (LUCENE-1873) Update site lucene-sandbox page
Date Tue, 01 Sep 2009 22:29:32 GMT


Steven Rowe commented on LUCENE-1873:

I think we should add generation of {{Contrib-Changes.html}} from {{contrib/CHANGES.txt}}
to the {{changes-to-html}} target in {{build.xml}}:

<exec executable="perl" input="contrib/CHANGES.txt" output="${}/Contrib-Changes.html"
  <arg value="${changes.src.dir}/"/>

and then link to it from near the top of {{lucene-sandbox/index.xml}}, something like:

  See <a href="">Contrib
CHANGES</a> for changes included in the current release.

> Update site lucene-sandbox page
> -------------------------------
>                 Key: LUCENE-1873
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 2.9
>         Attachments: LUCENE-1873.patch
> The page has misleading/bad info. One thing I would like to do - but I won't attempt
now (prob good for the modules issue) - is commit to one word - contrib or sandbox. I think
sandbox should be purged myself.
> The current page says that the sandbox is kind of a rats nest with various early stage
software that one day may make it into core - that info is outdated I think. We should replace
it, and also specify how the back compat policy works in contrib eg each contrib can have
its own policy, with the default being no policy.
> We should also drop the piece about being open to Lucene's committers and others - a
bit outdated.
> We should also either include the other contribs, or change the wording to indicate that
the list is only a sampling of the many contribs.

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:
For additional commands, e-mail:

View raw message