Re: [Gluster-Maintainers] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

[Aravinda VK]

This is awesome. Thanks to infra team for the great effort.

—
Aravinda Vishwanathapura
https://kadalu.io

> On 07-Oct-2020, at 3:16 PM, Deepshikha Khandelwal  wrote:
> 
> Hi folks,
> 
> We have initiated the migration process today. All the patch owners are 
> requested to move their existing patches from Gerrit[1] to Github[2].
> 
> The changes we brought in with this migration:
> 
> - The 'devel' branch[3] is the new default branch on GitHub to get away from 
> master/slave language.
> 
> - This 'devel' branch is the result of the merge of the current branch and 
> the historic repository, thus requiring a new clone. It helps in getting the 
> complete idea of tracing any changes properly to its origin to understand the 
> intentions behind the code.
> 
> - We have switched the glusterfs repo on gerrit to readonly state. So you 
> will not be able to merge the patches on Gerrit from now onwards. Though we 
> are not deprecating gerrit right now, we will work with the remaining 
> users/projects to move to github as well.
> 
> - Changes in the development workflow: 
> - All the required smoke tests would be auto-triggered on submitting a PR.
> - Developers can retrigger the smoke tests using "/recheck smoke" as 
> comment.
> - The "regression" tests would be triggered by a comment "/run 
> regression" from anyone in the gluster-maintainers[4] github group. To run 
> full regression, maintainers need to comment "/run full regression"
> 
> For more information you can go through the contribution guidelines listed in 
> CONTRIBUTING.md[5]
> 
> [1] https://review.gluster.org/#/q/status:open+project:glusterfs 
> 
> [2] https://github.com/gluster/glusterfs 
> 
> [3] https://github.com/gluster/glusterfs/tree/devel 
> 
> [4] https://github.com/orgs/gluster/teams/gluster-maintainers 
> 
> [5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md 
> 
> 
> Please reach out to us if you have any queries.
> 
> Thanks,
> Gluster-infra team
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers





___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

[Amar Tumballi]

Thanks for getting this done, Deepshika and Michael, and Infra team members.

Thanks everyone for valuable feedback during this process!

I personally hope this change will help glusterfs project to attract more
developers, and we can engage more closely with our developers!

Note that this would result in weeks of confusions, questions, and bugs in
workflow! We are trying to tune the workflow accordingly! Please try it
out, and give feedback! Once we start using we may figure out new things,
so jump in, and give it a try!

In case of any issues, raise a github issue,  or find some of us on
gluster.slack.com

Regards,
Amar



On Wed, Oct 7, 2020 at 3:16 PM Deepshikha Khandelwal 
wrote:

> Hi folks,
>
> We have initiated the migration process today. All the patch owners are
> requested to move their existing patches from Gerrit[1] to Github[2].
>
> The changes we brought in with this migration:
>
> - The 'devel' branch[3] is the new default branch on GitHub to get away
> from master/slave language.
>
> - This 'devel' branch is the result of the merge of the current branch and
> the historic repository, thus requiring a new clone. It helps in getting
> the complete idea of tracing any changes properly to its origin to
> understand the intentions behind the code.
>
> - We have switched the glusterfs repo on gerrit to readonly state. So you
> will not be able to merge the patches on Gerrit from now onwards. Though we
> are not deprecating gerrit right now, we will work with the remaining
> users/projects to move to github as well.
>
> - Changes in the development workflow:
> - All the required smoke tests would be auto-triggered on submitting a
> PR.
> - Developers can retrigger the smoke tests using "/recheck smoke" as
> comment.
> - The "regression" tests would be triggered by a comment "/run
> regression" from anyone in the gluster-maintainers[4] github group. To run
> full regression, maintainers need to comment "/run full regression"
>
> For more information you can go through the contribution guidelines listed
> in CONTRIBUTING.md[5]
>
> [1] https://review.gluster.org/#/q/status:open+project:glusterfs
> [2] https://github.com/gluster/glusterfs
> [3] https://github.com/gluster/glusterfs/tree/devel
> [4] https://github.com/orgs/gluster/teams/gluster-maintainers
> [5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md
>
> Please reach out to us if you have any queries.
>
> Thanks,
> Gluster-infra team
>


-- 
--
https://kadalu.io
Container Storage made easy!
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] ACTION REQUESTED: Migrate your glusterfs patches from Gerrit to GitHub

[Deepshikha Khandelwal]

Hi folks,

We have initiated the migration process today. All the patch owners are
requested to move their existing patches from Gerrit[1] to Github[2].

The changes we brought in with this migration:

- The 'devel' branch[3] is the new default branch on GitHub to get away
from master/slave language.

- This 'devel' branch is the result of the merge of the current branch and
the historic repository, thus requiring a new clone. It helps in getting
the complete idea of tracing any changes properly to its origin to
understand the intentions behind the code.

- We have switched the glusterfs repo on gerrit to readonly state. So you
will not be able to merge the patches on Gerrit from now onwards. Though we
are not deprecating gerrit right now, we will work with the remaining
users/projects to move to github as well.

- Changes in the development workflow:
- All the required smoke tests would be auto-triggered on submitting a
PR.
- Developers can retrigger the smoke tests using "/recheck smoke" as
comment.
- The "regression" tests would be triggered by a comment "/run
regression" from anyone in the gluster-maintainers[4] github group. To run
full regression, maintainers need to comment "/run full regression"

For more information you can go through the contribution guidelines listed
in CONTRIBUTING.md[5]

[1] https://review.gluster.org/#/q/status:open+project:glusterfs
[2] https://github.com/gluster/glusterfs
[3] https://github.com/gluster/glusterfs/tree/devel
[4] https://github.com/orgs/gluster/teams/gluster-maintainers
[5] https://github.com/gluster/glusterfs/blob/master/CONTRIBUTING.md

Please reach out to us if you have any queries.

Thanks,
Gluster-infra team
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers