Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Lucene: Java-Dev

[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt

 

 

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded


jira at apache

Jul 19, 2012, 2:57 PM

Post #1 of 5 (73 views)
Permalink
[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt

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

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

If i don't see any objections, i'll start the grunt work to merge all the files into solr/CHANGES.txt sometime next week.

> 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 [at] frisbe:~/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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Jul 25, 2012, 4:33 AM

Post #2 of 5 (69 views)
Permalink
[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt [In reply to]

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

Jan Høydahl commented on SOLR-3650:
-----------------------------------

+1

> 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 [at] frisbe:~/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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Jul 30, 2012, 5:43 PM

Post #3 of 5 (61 views)
Permalink
[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt [In reply to]

[ 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 [at] frisbe:~/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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Jul 30, 2012, 6:40 PM

Post #4 of 5 (61 views)
Permalink
[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt [In reply to]

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

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

contrib/uima and contrib/extraction ...

Committed revision 1367384. - trunk
Committed revision 1367385. - 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 [at] frisbe:~/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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Aug 1, 2012, 11:48 AM

Post #5 of 5 (60 views)
Permalink
[jira] [Commented] (SOLR-3650) eliminate solr/contrib/*/CHANGES.txt [In reply to]

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

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

DIH...

Committed revision 1368190. - trunk
Committed revision 1368191. - 4x

...this should be done now, but i want to sanity check all the packaging before resolving.



> 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 [at] frisbe:~/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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.