[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
+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 Sent: Wednesday, March 16, 2022 2:12 PM To: geode 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
+1 From: Owen Nichols Sent: Wednesday, March 16, 2022 2:12 PM To: geode 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
+1 From: Nabarun Nag Sent: Wednesday, March 16, 2022 2:36 PM To: geode Subject: Re: [PROPOSAL] annul support/1.15 +1 From: Owen Nichols Sent: Wednesday, March 16, 2022 2:12 PM To: geode 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
+1 From: Owen Nichols Date: Wednesday, March 16, 2022 at 2:12 PM To: geode 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
+1 From: Owen Nichols Sent: Wednesday, March 16, 2022 2:12 PM To: geode 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
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 Date: Wednesday, March 16, 2022 at 3:11 PM To: dev@geode.apache.org Subject: Re: [PROPOSAL] annul support/1.15 +1 From: Owen Nichols Sent: Wednesday, March 16, 2022 2:12 PM To: geode 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
