Migrate bugzilla workflow to github issues workflow #824
Description
The issue is for migrating the current issues tracking from bugzilla to github.
Discussions on this is happening on mailing list, and few of the references are below:
- https://lists.gluster.org/pipermail/gluster-infra/2020-February/006030.html
- https://lists.gluster.org/pipermail/gluster-infra/2020-February/006009.html
- https://lists.gluster.org/pipermail/gluster-infra/2020-February/006040.html
Now, as described in all these emails, there would be below steps to watch for:
- Send patch to change https://github.com/gluster/glusterfs/blob/master/.github/ISSUE_TEMPLATE
- Migrate all open bugs from bugzilla.redhat.com and create corresponding issues in github.
- Expect a lot of emails (~300) as so many new issues would be created.
- A draft code of how the migration would happen is posted @ https://github.com/amarts/gluster-bugzilla-migration - Suggestions/ feedback welcome.
- Make changes in current developer / contributing workflow to say 'create issues' instead of 'open a bug report', and change URLs from github.
- Across the board documentation changes.