[Gluster-infra] [Bug 1564130] New: need option 'cherry-pick to release-x.y' in reviews

bugzilla at redhat.com bugzilla at redhat.com
Thu Apr 5 12:35:51 UTC 2018


            Bug ID: 1564130
           Summary: need option 'cherry-pick to release-x.y' in reviews
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: atumball at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    gluster-infra at gluster.org, jeff at pl.atyp.us,
                    srangana at redhat.com

# Description of problem:

Today, below is the process to send a patch to release branch:

* clone the bug in relevant branch
* author has to submit the patches once they land in master, with this new bug
id (or same issue, if its RFE),
* Make sure 'Change-Id:' is same.
* Push the patch to release branch.

This is not so simple for someone who is not so regular contributor to gluster
project, and also a waste of time for everyone as all-most all of it can be

Idea is to have a review command called 'cherry-pick to $branch-name', which
triggers a job, which clones the bug from the patchset, and takes the new bug,
and will make sure the new bug is updated in release branch after applying the
patch on top of release branch.

There are possibilities of failure. It is OK for failure in case of merge
conflict, but still it will save time for user because the bug can be
automatically cloned.

Expectation is that, (if possible) new bug id gets posted to patchset as result
of the command. On success the URL of new patch.

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Oq7bmdiO5G&a=cc_unsubscribe

More information about the Gluster-infra mailing list