lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3164) consolidate various CHANGES.txt into two files: lucene and solr
Date Tue, 31 May 2011 04:43:47 GMT

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

Robert Muir commented on LUCENE-3164:
-------------------------------------

{quote}
There is a risk that changes in contribs/modules would clutter the core changes. For example,
today, even small changes in contrib/benchmark are listed in the changes file. But when this
becomes part of the global changes file, not sure if all bm changes would be adequate to be
listed there?
{quote}

Well, I agree there is that risk, especially if releases continue to be yearly instead of
more often.

However, I think if we release more often, the risk subsides, because we would be presenting
regular releases with a manageable set of consolidated CHANGES.

In other words, if you combine the core+contrib+benchmark+grouping changes in 3.2, is it really
cluttered?
I think the same goes for the solr changes.

Personally, if I was looking at the lucene CHANGES for version X, I would want to know that
there is a new NRTCachingDirectory, that there are performance improvements to the Highlighter,
and that lucene now supports result grouping... 


> consolidate various CHANGES.txt into two files: lucene and solr
> ---------------------------------------------------------------
>
>                 Key: LUCENE-3164
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3164
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Robert Muir
>
> There are CHANGES.txt files everywhere: lucene/contrib has a CHANGES.txt, the benchmark
package has its own CHANGES.txt, in trunk all the modules have their own CHANGES.txt, and
each solr contrib has its own CHANGES.txt
> I propose we merge these files into a CHANGES.txt for each "product" we make. so that
means lucene/CHANGES.txt and solr/CHANGES.txt

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message