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 t
+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 maint
+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 premature
+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
Se
+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 abando
+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 premature
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 P
