You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Owen Nichols <on...@vmware.com> on 2022/03/16 21:12:02 UTC
[PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] re-cut support/1.15
Posted by Owen Nichols <on...@vmware.com>.
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.
On May 6, 2022 at 11:17:14 AM PDT, Robert Houghton <rh...@vmware.com> wrote:
I would like GEODE-1028 [1] to be considered for support/1.15. It is a significant change to the build logic, and I think would be a benefit to inclusion in the release branch. PR to develop is available[2]
Thank you,
-Robert Houghton
[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-10283&data=05%7C01%7Conichols%40vmware.com%7C5382a71cb8c24e3c712c08da2f8ca423%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637874578340537043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XM4pI60cfPKki2BqhAZPQLdiXAhRy9bv1hghc3NFqho%3D&reserved=0
[2 ]https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F7600&data=05%7C01%7Conichols%40vmware.com%7C5382a71cb8c24e3c712c08da2f8ca423%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637874578340537043%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Wf8pEaN3wHtpI4WoRpE%2FKrkZpoT8a7GqZgXRzu7kZl4%3D&reserved=0
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] annul support/1.15
Posted by Robert Houghton <rh...@vmware.com>.
I would like GEODE-1028 [1] to be considered for support/1.15. It is a significant change to the build logic, and I think would be a benefit to inclusion in the release branch. PR to develop is available[2]
Thank you,
-Robert Houghton
[1] https://issues.apache.org/jira/browse/GEODE-10283
[2 ]https://github.com/apache/geode/pull/7600
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] re-cut support/1.15
Posted by Owen Nichols <on...@vmware.com.INVALID>.
Hello Geode Community, counting the labels in Jira I see:
May 6: 1 needsTriage and 2 blocks-1.15.0.
May 20: 0 needsTriage and 3 blocks-1.15.0.
June 8: 0 needsTriage and 0 blocks-1.15.0. Yay!
At this time, please consider support/1.15 “frozen”. If there are any further changes needed, 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 <on...@vmware.com>
Date: Monday, May 9, 2022 at 10:31 AM
To: dev@geode.apache.org <de...@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 should merge their own PRs.
If your backport will take some while, add the "blocks-1.15.0" label in Jira.
From: Owen Nichols <on...@vmware.com>
Date: Friday, May 6, 2022 at 10:47 AM
To: dev@geode.apache.org <de...@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 "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] https://tinyurl.com/5h58766f
[2] https://tinyurl.com/2p8bje4n
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] re-cut support/1.15
Posted by Owen Nichols <on...@vmware.com.INVALID>.
Hello Geode Community, counting the labels in Jira I see:
May 6: 1 needsTriage and 2 blocks-1.15.0.
May 20: 0 needsTriage and 3 blocks-1.15.0.
Looks like some progress. Please continue to use the above labels to raise any issues.
-1.15.0 Release Manager
From: Owen Nichols <on...@vmware.com>
Date: Monday, May 9, 2022 at 10:31 AM
To: dev@geode.apache.org <de...@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 should merge their own PRs.
If your backport will take some while, add the "blocks-1.15.0" label in Jira.
From: Owen Nichols <on...@vmware.com>
Date: Friday, May 6, 2022 at 10:47 AM
To: dev@geode.apache.org <de...@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 "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] https://tinyurl.com/5h58766f
[2] https://tinyurl.com/2p8bje4n
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] re-cut support/1.15
Posted by Owen Nichols <on...@vmware.com>.
** 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 should merge their own PRs.
If your backport will take some while, add the "blocks-1.15.0" label in Jira.
From: Owen Nichols <on...@vmware.com>
Date: Friday, May 6, 2022 at 10:47 AM
To: dev@geode.apache.org <de...@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 "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] https://tinyurl.com/5h58766f
[2] https://tinyurl.com/2p8bje4n
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] re-cut support/1.15
Posted by Owen Nichols <on...@vmware.com>.
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] https://tinyurl.com/5h58766f
[2] https://tinyurl.com/2p8bje4n
From: Anthony Baker <ba...@vmware.com>
Date: Friday, May 6, 2022 at 10:19 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] annul support/1.15
Posted by Anthony Baker <ba...@vmware.com>.
Owen, with all the recent work I think we are in an excellent position to resume work on the 1.15 release. While there are a few thing still outstanding, let’s go ahead and recut the release branch as of Monday, 2022-05-09. Would you be willing to resume release manager duties?
@Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”).
Thanks,
Anthony
> On Mar 16, 2022, at 2:12 PM, Owen Nichols <on...@vmware.com> wrote:
>
> Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
>
> If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
>
> Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
>
> Thanks,
> -Geode 1.15.0 Release Manager
>
>
Re: [PROPOSAL] annul support/1.15
Posted by Jens Deppe <jd...@vmware.com>.
+1
From: Owen Nichols <on...@vmware.com>
Date: Wednesday, March 16, 2022 at 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] annul support/1.15
Posted by Darrel Schneider <da...@vmware.com>.
+1
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Wednesday, March 16, 2022 2:36 PM
To: geode <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
+1
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Wednesday, March 16, 2022 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] annul support/1.15
Posted by Nabarun Nag <nn...@vmware.com>.
+1
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Wednesday, March 16, 2022 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] annul support/1.15
Posted by Donal Evans <do...@vmware.com>.
+1
Given the amount of work that it's apparent is still needed for 1.15 to be ready to release, it seems like the sensible thing to do to reset and try again once we're closer to being done. I don't think we would have cut the branch when we did if we'd known what work was still left, and maintaining a long-lived release branch is just adding unnecessary overhead to our processes.
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Wednesday, March 16, 2022 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] annul support/1.15
Posted by Owen Nichols <on...@vmware.com>.
Thanks for all the responses. Sounds like there is no need to wait until Monday to declare consensus; I'll go ahead and get started now.
The result will be as if the branch cut had never happened.
Thanks,
-Geode 1.15.0 Release Manager
From: Dale Emery <de...@vmware.com>
Date: Wednesday, March 16, 2022 at 3:11 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [PROPOSAL] annul support/1.15
+1
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Wednesday, March 16, 2022 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager
Re: [PROPOSAL] annul support/1.15
Posted by Dale Emery <de...@vmware.com>.
+1
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Wednesday, March 16, 2022 2:12 PM
To: geode <de...@geode.apache.org>
Subject: [PROPOSAL] annul support/1.15
Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch.
If this proposal is approved, I will archive support/1.15 as support/1.15.old, revert develop's numbering to 1.15.0, and bulk-update all Jira tickets fixed in 1.16.0 to fixed in 1.15.0 instead. Build numbering would start from 1.15.0-build.1000 to easily distinguish pre- and post- recut.
Please vote/discuss with a goal of reaching consensus by 3PM PDT Monday Mar 21.
Thanks,
-Geode 1.15.0 Release Manager