https://bugzilla.redhat.com/show_bug.cgi?id=1428036
Bug ID: 1428036 Summary: Update rfc.sh to check/request issue # when a commit is an “rfc” Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: nig...@redhat.com Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Gluster intends to move to github to track features being delivered against the code base. Read the announcement here: http://lists.gluster.org/pipermail/gluster-devel/2017-February/052203.html Specifics of the github process here: https://hackmd.io/s/BkgH8sdtg# Towards the above the following change is requested: ---------------------------------------------------- Update rfc.sh to check/request issue # when a commit is an “rfc”: Change: https://github.com/gluster/glusterfs/blob/master/rfc.sh This is more a helping hand for the process, when a bug ID is not entered, it would be helpful to check if the commit message has a Fixes or Updates issue# comment, else prompt and edit the commit message accordingly The prompt can just be for an issue number, and not specifically "Updates" or "Fixes", just to keep it light. If the commit really is the last fix the submitter/reviewer should be able to handle the request for the appropriate keyword. For glusterfs-specs, we use git-review instead of rfc.sh, so a test needs to be enforced somewhere in that workflow for issue# presence (even reviewers can request for the same if it is missing), if possible lets automate it, else we will have to depend on reviewers -- 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=ZVFvTHSRm8&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra