[Gluster-infra] [Bug 1423002] New: Changes needed in infra to accommodate move to github for issue tracking and updates

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1423002

            Bug ID: 1423002
           Summary: Changes needed in infra to accommodate move to github
                    for issue tracking and updates
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Assignee: bugs at gluster.org
          Reporter: srangana at redhat.com
                CC: bugs at gluster.org, gluster-infra at gluster.org



This mail [1] and this text [2] details the new workflow that we intend to use,
which is closing out of bugzilla and moving to github issues, for all feature
and bug tracking needs.

This bug is filed based on my understanding of things that need to change in
the infrastructure (i.e scripts etc. not additional infrastructure
requirements).

We may need multiple people changing te various things mentioned here, in which
case we can use this as the tracker bug for all changes.

[1] Mail regarding movement to github:
http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html

[2] Text detailing the github workflow: http://bit.ly/2kIoFJf

Changes needed:
A) rfc.sh needs:
  - https://github.com/gluster/glusterfs/blob/master/rfc.sh
  - Prompt for issue #
  - Prompt for Fixes or Updates for the issue
  - Modify commit with the details as needed

B) Jenkins needs:
Bug version and branch:
 
https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/compare-bug-version-and-git-branch.sh
  - This should now check and see if the issue mentioned has the label
"RequiredIn: X.Y", when a commit for that branch is made.
  - If the commit is against master, this should also check if the issue is
still open

C) WorkerAnt needs:
  1) patchset-created
    - https://github.com/gluster/gerrit-hooks/blob/master/patchset-created
    - Update all issues that are mentioned with the details of the patchset
    - Update asignee for the issues mentioned as well, based on the committer

  2) patchset-merged
    - https://github.com/gluster/gerrit-hooks/blob/master/change-merged
    - Issues will get auto updated about the patchset (this is part of what
github does anyway), and even closed if there is a mention of "Fixes"
    - We additionally need to do some label movement as follows, for all issues
referenced with "Fixes" in the message (i.e issues that would get closed with
this commit)
      - Remove: RequiredIn: X.Y (for non-master branches ONLY)
      - Add: Commited in: X.Y
        - Gets added for master as well

-- 
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=0Hsv4XLYMD&a=cc_unsubscribe