You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2016/05/23 13:43:12 UTC
[jira] [Updated] (STORM-1490) Update storm-merge.py to be full
featured
[ https://issues.apache.org/jira/browse/STORM-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated STORM-1490:
---------------------------------------
Assignee: (was: Robert Joseph Evans)
> Update storm-merge.py to be full featured
> -----------------------------------------
>
> Key: STORM-1490
> URL: https://issues.apache.org/jira/browse/STORM-1490
> Project: Apache Storm
> Issue Type: Improvement
> Components: build
> Reporter: Robert Joseph Evans
>
> storm-merge.py should optionally do more then just print out the merge command.
> At a minimum it should
> 1. update the branch you are trying to merge to
> 2. create the branch integration branch (based off of the first branch)
> 3. run the merge
> 4. update the changelog (unless we just want this to go away)
> 5. run some sanity tests (minimum build, ideally some tests and RAT too)
> 6. merge the integration back to the main branch
> 7. push the result back to apache
> It would also really be nice if it could offer the ability to cherry-pick a pull request made on another branch. Updating things as needed
> If we want the changelog to go away it would not be too hard to combine a JIRA query with a git log to regenerate that too. But that might be a separate tool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)