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

Hoss Man commented on SOLR-3650:
--------------------------------

Finished these...

* solr/contrib/analysis-extras/CHANGES.txt
* solr/contrib/clustering/CHANGES.txt
* solr/contrib/langid/CHANGES.txt

...and committed checkpoint to reduce risk of conflicts as other people edit 
solr/CHANGES.txt...

Committed revision 1367377. - trunk
Committed revision 1367378. - 4x


                
> eliminate solr/contrib/*/CHANGES.txt
> ------------------------------------
>
>                 Key: SOLR-3650
>                 URL: https://issues.apache.org/jira/browse/SOLR-3650
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 4.0, 5.0
>
>
> There was discussion a long while back about eliminating the plethora of 
> CHANGES.txt files in various lucene contribs/modules and consolidating into 
> lucene/CHANGES.txt to prevent "hiding" things from users who may not 
> know/think/remember to check each of the individual contirbs/modules.
> this is long done and dealt with under "lucene/", but on the "solr/" side we 
> still have a multitude of CHANGES.txt files in contribs that are 
> inconsistently used to record features/fixes in those contribs (frequently 
> they get listed in solr/CHANGES.txt instead)
> We should eliminate these contrib/*/CHANGES.txt files completely, and merge 
> all of the existing items in them into the apropriate version & section of 
> solr/CHANGES.txt
> {noformat}
> hossman@frisbee:~/lucene/dev$ find -name CHANGES.txt
> ./solr/CHANGES.txt
> ./solr/contrib/langid/CHANGES.txt
> ./solr/contrib/dataimporthandler/CHANGES.txt
> ./solr/contrib/clustering/CHANGES.txt
> ./solr/contrib/extraction/CHANGES.txt
> ./solr/contrib/uima/CHANGES.txt
> ./solr/contrib/analysis-extras/CHANGES.txt
> ./lucene/CHANGES.txt
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to