It is perhaps on Amar to send the PR with the changes - but that would kind of make the approval/merge process a bit muddled? How about a PR being sent for review and then merged in? On Mon, 12 Oct 2020 at 19:22, Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote: > > > > On Thu, Oct 8, 2020 at 8:10 AM Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote: >> >> On Wed, Oct 7, 2020 at 7:33 AM Sunil Kumar Heggodu Gopala Acharya <sheggodu@xxxxxxxxxx> wrote: >>> >>> >>> Regards, >>> >>> Sunil kumar Acharya >>> >>> >>> >>> >>> On Wed, Oct 7, 2020 at 4:54 PM Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote: >>>> >>>> >>>> >>>> On Wed, Oct 7, 2020 at 5:46 AM Deepshikha Khandelwal <dkhandel@xxxxxxxxxx> wrote: >>>>> >>>>> >>>>> - 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" >>>>> >>>>> [4] https://github.com/orgs/gluster/teams/gluster-maintainers >>>> >>>> >>>> There are a lot of people in that group that haven't been involved with Gluster for a long time. >>> >>> Also there are new contributors, time to update! >> >> >> Who is going to do this? I don't have the necessary privs. > > > Anyone? > > -- > > Kaleb > _______________________________________________ > maintainers mailing list > maintainers@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/maintainers -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> _______________________________________________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
