[Gluster-Maintainers] Move out of bugzilla to github issues --> for everything...

[Shyam]

After contributing/listening in to the exchange on moving out of 
bugzilla to github for glusterfs repository, I think there are a few 
questions to be answered before the move. This will take time and hence 
not make it prior to the 3.11 time frame (I am thinking such moves are 
better just post a release).

Hence, we push this to a point post 3.11 (possibly 4.0) where we can 
come back with answers to the questions and observations posted on move.

Thanks for the discussion all!

We will however continue using github for the release planning and also 
for feature/major fixes, backlog tracking. The idea being use github for 
the features and bugzilla for bugs and avoid duplication of effort.

I am writing up a workflow document, that will complete the move to 
using github for features (that we started with 3.10), to be shared with 
gluster-devel. This give us an opportunity to beef up this change and 
reinforce it with 3.11 and 4.0.

Heads up!
The above possibly still requires work on 3 scripts/infrastructure pieces,
1. Change 
https://github.com/gluster/gerrit-hooks/blob/master/patchset-created to 
post to github issues when they are referenced in the commit message for 
rfc submissions
2. Change https://github.com/gluster/glusterfs/blob/master/rfc.sh to 
possibly prompt for issue # when an rfc submission is being made
3. gerrit to provide links to github issues, when they appear in the 
commit message
   - As an example consider this from the golang page: 
https://go-review.googlesource.com/#/c/37148/

There could be others, but I need to discover them as we talk about this 
more on devel.

Shyam

On 02/08/2017 02:04 PM, Shyam wrote:
> Hi,
>
> In today's maintainers meeting I wanted to introduce what it would take
> us to move away from bugzilla to github. The details are in [1].
>
> Further to this, below is a mail detailing the plan(s) and attention
> needed to make this happen. Further I am setting up a maintainer meet on
> Friday 10th Feb, 2017, to discuss this plan and also discuss,
> - Focus areas: ownership and responsibility
> - Backlog population into github
>
> Request that maintainers attend this, as without a quorum we *cannot*
> make this move. If you are unable to attend, the please let us know any
> feedback on these plans that we need to consider.
>
> Calendar and plans for moving away from bugzilla to gihub:
> 1) Arrive maintainer consensus on the move
>   - 15th Feb, 2017
>   - This would require understanding [1] and figuring out if all
> requirements are considered
>   - We will be discussing [1] in detail on the coming Friday.
>
> 2) Announce plans to the larger development and user community for
> consensus
>   - Close consensus by 22nd Feb, 2017
>
> 3) (request and) Work with Infra folks for worker ant like integration
> to github instead of bugzilla
>   - Date TBD (done in parallel from the beginning)
>
> <<Assuming we are able to get (3) done by 24th Feb>>
>
> 4) Announce migration plans to larger community, calling out a 2 week
> window, after which bugzilla will be closed (available for historical
> reasons), and gerrit will also not accept bug IDs for changes
>   - 27th Feb, 2017
>
> 5) Close bugzilla and update gerrit as needed
>   - 10th Feb, 2017 weekend
>
> 6) Go live on the weekend specified in (5)
>
> Shyam
> [1] http://bit.ly/2kIoFJf
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers