https://bugzilla.redhat.com/show_bug.cgi?id=1564130
Bug ID: 1564130 Summary: need option 'cherry-pick to release-x.y' in reviews Product: GlusterFS Version: mainline Component: project-infrastructure Severity: high Assignee: b...@gluster.org Reporter: atumb...@redhat.com CC: amukh...@redhat.com, b...@gluster.org, gluster-infra@gluster.org, j...@pl.atyp.us, srang...@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 automated. 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 _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra