lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1873) Update site lucene-sandbox page
Date Mon, 31 Aug 2009 15:29:32 GMT

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

Steven Rowe commented on LUCENE-1873:
-------------------------------------

I'm +1 on switching away from "Sandbox" (no longer used at all) to Contrib.

Before you posted your patch, I had written up a new intro for the contrib index.html - feel
free to take any of this or ignore it :) :

{code:html}
      <p>
        The Lucene Java project also contains a workspace, Lucene Contrib
        (formerly known as the Lucene Sandbox), that is open both to all Lucene 
        Java core committers and to developers whose commit rights are 
        restricted to the Contrib workspace; these developers are referred to 
        as "Contrib committers".  The Lucene Contrib workspace hosts the 
        following types of packages:
      </p>
      <ul>
        <li>Various third party contributions.</li>
        <li>
          Contributions with third party dependencies - the Lucene Java core
          distribution has no external runtime dependencies.
        </li>
        <li>
          New ideas that are intended for eventual inclusion into the Lucene 
          Java core.
        </li>
      </ul>
      <p>
        Users are free to experiment with the components developed in the
        Contrib workspace, but Contrib packages will not necessarily be
        maintained, particularly in their current state. The Lucene Java core 
        backwards compatibility commitments (see
        <a href="http://wiki.apache.org/lucene-java/BackwardsCompatibility"
          >http://wiki.apache.org/lucene-java/BackwardsCompatibility</a>)
        do not necessarily extend to the packages in the Contrib workspace.
        See the README.txt file for each Contrib package for details.  If the
        README.txt file does not address its backwards compatibility
        commitments, users should assume it does not make any compatibility
        commitments.
      </p>
{code}

> Update site lucene-sandbox page
> -------------------------------
>
>                 Key: LUCENE-1873
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1873
>             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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message