Bug 1558335
| Summary: | gluster-block: discontinue gerrit | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Prasanna Kumar Kalever <prasanna.kalever> |
| Component: | project-infrastructure | Assignee: | bugs <bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | amukherj, bugs, gluster-infra, nigelb, pkarampu, sabose, vbellur, xiubli |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-12 14:58:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Prasanna Kumar Kalever
2018-03-20 04:30:03 UTC
FWIW (and out of curiosity too), it'd be worth to mention why did we decide to move away from gerrit :-) Okay, I'm creating this checklist on the fly here. 1. Do you have a team on github with the correct people having commit access? [Yes/No] 2. Are all your existing review requests closed on github? [Yes/No] 3. Do you expect new review requests on gerrit to be rejected? [Yes/No] 4. I will be switching your Gerrit repo to read-only and removing the sync to Github. Please acknowledge that this is okay. [Yes/No] (In reply to Atin Mukherjee from comment #1) > FWIW (and out of curiosity too), it'd be worth to mention why did we decide > to move away from gerrit :-) 1. Currently the upstream RFE's/issues/bugs/milestones are tracked in github, where as we encourage patches to be pushed to gerrit only. It is good to have everything at one place (As a fact supporting both is not possible) 2. Not everyone knows gerrit, for example we see new contributors directly send patches to github and asking them to send to gerrit looks an extra hop. 3. Personally, I do not see a real benefit in using gerrit and not github. 4. Also having everything at one place give us opportunity to address/answer the github issues faster (as we look at github more often than before) Others can add/correct. (In reply to Nigel Babu from comment #2) > Okay, I'm creating this checklist on the fly here. > > 1. Do you have a team on github with the correct people having commit access? > [Yes/No] Yes > > 2. Are all your existing review requests closed on github? > [Yes/No] do you mean to ask in gerrit ? We have open issues in github and gerrit, but all the commits are from within the team, so we can manage to send new review request and abandon the older once. Not sure if that answers your question though. > > 3. Do you expect new review requests on gerrit to be rejected? > [Yes/No] Yes, may be with some good message if possible. > > 4. I will be switching your Gerrit repo to read-only and removing the sync > to Github. Please acknowledge that this is okay. > [Yes/No] Yes. @pranith, @vijay Please acknowledge. Thanks! (In reply to Prasanna Kumar Kalever from comment #3) > (In reply to Atin Mukherjee from comment #1) > > FWIW (and out of curiosity too), it'd be worth to mention why did we decide > > to move away from gerrit :-) > > 1. Currently the upstream RFE's/issues/bugs/milestones are tracked in > github, where as we encourage patches to be pushed to gerrit only. It is > good to have everything at one place (As a fact supporting both is not > possible) > > 2. Not everyone knows gerrit, for example we see new contributors directly > send patches to github and asking them to send to gerrit looks an extra hop. > > 3. Personally, I do not see a real benefit in using gerrit and not github. > > 4. Also having everything at one place give us opportunity to address/answer > the github issues faster (as we look at github more often than before) > > Others can add/correct. This was also asked multiple times by heketi team. So we also felt like it is better. This is complete |