You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2018/04/06 20:58:00 UTC
[jira] [Commented] (SOLR-7627) Either automate or stop listing the
"Versions of Major Components" in CHANGES.txt
[ https://issues.apache.org/jira/browse/SOLR-7627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428987#comment-16428987 ]
Steve Rowe commented on SOLR-7627:
----------------------------------
FYI {{get_solr_init_changes()}} in {{addVersion.py}}, which is run by the release manager after branching for a release, automates filling out this {{CHANGES.txt}} section, pulling versions from {{ivy-versions.properties}}. This won't keep the versions in sync though.
> Either automate or stop listing the "Versions of Major Components" in CHANGES.txt
> ---------------------------------------------------------------------------------
>
> Key: SOLR-7627
> URL: https://issues.apache.org/jira/browse/SOLR-7627
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Priority: Major
>
> At some point along the way, we got in the practice of having a "Versions of Major Components" sub-section in changes.txt for each release ... in addition to the normal practice of recording the individual Jiras when deps are upgraded.
> maintaining this sub-section accurately seems very tedious and error prone (see SOLR-7626) so it seems like we should either:
> * stop doing this completely and trust the users to look at the ivy files for the dependencies
> * find a way to automate this so we don't have to do it manually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org