[jira] [Commented] (LUCENE-5902) Add bumpVersion script to increment version after release branch creation

["Ryan Ernst (JIRA)" <ji...@apache.org>]

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

Ryan Ernst commented on LUCENE-5902:
------------------------------------

I have most of this ready to go, but I want to get opinions are part of the workflow.  My current idea is to run this on the most specific branch first.  So if it is a bugfix release, it would be run on the release branch.  You would then run the script again on 4x, with the commit id of the change to the release branch.  It would do the merge, and make the appropriate changes on 4x (ie not changing LATEST or example configs).  Does this seem like a reasonable workflow? I just want to minimize the extra work that people have to do, even in merging upwards.

> Add bumpVersion script to increment version after release branch creation
> -------------------------------------------------------------------------
>
>                 Key: LUCENE-5902
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5902
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Ryan Ernst
>
> Thanks to LUCENE-5898 there are many less places to increment version.  However, I still think this script can be useful in automating the entire process (minus the commit).  This would:
> * Add new sections to {{lucene/CHANGES.txt}} and {{solr/CHANGES.txt}}
> * Add new version constant
> * Change {{LATEST}} value
> * Change {{version.base}} in {{lucene/version.properties}}
> * Change version used in solr example configs
> * Create a BWC index and test if necessary



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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