You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2013/10/02 02:21:24 UTC
[jira] [Resolved] (LUCENE-3164) consolidate various CHANGES.txt
into two files: lucene and solr
[ https://issues.apache.org/jira/browse/LUCENE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved LUCENE-3164.
------------------------------
Resolution: Fixed
this was resolved long, long ago....
> consolidate various CHANGES.txt into two files: lucene and solr
> ---------------------------------------------------------------
>
> Key: LUCENE-3164
> URL: https://issues.apache.org/jira/browse/LUCENE-3164
> Project: Lucene - Core
> 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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org