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
> 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: [DIS
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
__
From: Nabarun Nag
Sent: Friday, March 19, 2021 10:31 AM
To: dev@geode.apache.org
Subject: [DISCUSS] Backporting to support branches
Hi,
I would like to propose that if any JIRA needs to be backported to support
branches:
For Developers:
* Add the lab
: [DISCUSS] Backporting to support branches
Hi,
I would like to propose that if any JIRA needs to be backported to support
branches:
For Developers:
* Add the label "blocks-1.1x" to the JIRA ticket
* There is no need to send out a PROPOSAL email to dev
* Just create the che
Hi,
I would like to propose that if any JIRA needs to be backported to support
branches:
For Developers:
* Add the label "blocks-1.1x" to the JIRA ticket
* There is no need to send out a PROPOSAL email to dev
* Just create the cherry-picked PR to the support branch and tag the
Rel
