, in addition to adding one of the labels above, please also
email the dev list, otherwise I will soon begin preparing RC1 for voting next
week.
-1.15.0 Release Manager
From: Owen Nichols
Date: Monday, May 9, 2022 at 10:31 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] re-cut support/1.15
9, 2022 at 10:31 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] re-cut support/1.15
** The support/1.15 branch has now been (re)cut and develop is now 1.16. **
Please use your best judgement in determining what to backport.
PRs against support/1.15 are welcome (but optional!). Committers
locks-1.15.0" label in Jira.
From: Owen Nichols
Date: Friday, May 6, 2022 at 10:47 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] re-cut support/1.15
Great news! I would be delighted to continue as Release Manager for 1.15.0.
To track progress toward code-complete, I will monitor the &q
Sounds great, Robert. Once your fix is on develop, no further approval is
needed to backport. Use your best judgement (or feel free to discuss on the dev
list if you are unsure). If backporting will take some while, add the
blocks-1.15.0 label to be sure this doesn’t slip through the cracks.
Great news! I would be delighted to continue as Release Manager for 1.15.0.
To track progress toward code-complete, I will monitor the "needsTriage" and
"blocks-1.15.0" labels (for Affects Version = 1.15.0). Currently I see 1
needsTriage [1] and 2 blocks-1.15.0 [2].
[1]
