[Gluster-devel] Switching GlusterFS upstream bugs to Github issues
sankarshan at kadalu.io
Fri Mar 13 03:49:07 UTC 2020
Thank you for making this happen. This is the first phase of adopting
a more GitHub based development workflow including actions.
On Thu, 12 Mar 2020 at 21:29, Deepshikha Khandelwal <dkhandel at redhat.com> wrote:
> Hi everyone,
> We have migrated most of the current upstream bugs(attached below) from the GlusterFS community Bugzilla product to Github issues.
> 1. All the issues created as a part of a migration will have Bugzilla URL, description, comments history, Github labels ('Migrated', 'Type: Bug', Prio) with a list of assignees.
> 2. All the component's bug except project-infrastructure will go to gluster/glusterfs repo.
> 3. project-infrastructure component's bugs will migrate under gluster/project-infrastructure repo.
> 4. We are freezing the GlusterFS community product on Bugzilla. It will be closed for new bug entries. You have to create an issue on Github repo from now onwards.
> 5. All the bugs have been closed on Bugzilla with the corresponding Github issue URL.
> 6. The changes have been reflected in the developer contributing workflow .
> 7. 'Migrated' and 'Type: Bug' GitHub labels has been added on the issues.
> Discussions on this are happening on the mailing list, and few of the references are below:
>  https://github.com/gluster/glusterfs/blob/master/.github/ISSUE_TEMPLATE
> Let us know if you see any issues.
> Thank you,
sankarshan at kadalu.io | TZ: UTC+0530
kadalu.io : Making it easy to provision storage in k8s!
More information about the Gluster-devel