Re: [DISCUSS] Backporting to support branches

2021-06-29 Thread Nabarun Nag
roves it makes sense. Regards Nabarun From: Jacob Barrett Sent: Tuesday, June 29, 2021 4:44 PM To: dev@geode.apache.org Subject: Re: [DISCUSS] Backporting to support branches Why not a model where the release manager is a blocking review and let the author merge onl

Re: [DISCUSS] Backporting to support branches

2021-06-29 Thread Jacob Barrett
; To: dev@geode.apache.org > Subject: Re: [DISCUSS] Backporting to support branches > > Hi Naba, is it still the case that only you will merge the PRs to > support/1.14? Or can committers merge their own 1.14 PRs anytime after you > have approved the PR? > > I sometimes forget to c

Re: [DISCUSS] Backporting to support branches

2021-06-29 Thread Nabarun Nag
free to ping me when all your testing is done and then I will take the necessary steps. Regards, Nabarun From: Owen Nichols Sent: Tuesday, June 29, 2021 3:51 PM To: dev@geode.apache.org Subject: Re: [DISCUSS] Backporting to support branches Hi Naba, is it still

Re: [DISCUSS] Backporting to support branches

2021-06-29 Thread Owen Nichols
Hi Naba, is it still the case that only you will merge the PRs to support/1.14? Or can committers merge their own 1.14 PRs anytime after you have approved the PR? I sometimes forget to create my PRs in Draft mode, and may still be running additional tests, so I'd prefer not to have anyone but

Re: [DISCUSS] Backporting to support branches

2021-03-19 Thread Nabarun Nag
Just a small change, a PR against the support branch is enough. (No need to add reviewers etc.). I just realized we can filter on a branch in the PR list. Regards, Nabarun From: Nabarun Nag Sent: Friday, March 19, 2021 10:31 AM To: dev@geode.apache.org Subject: