Weeks since support/1.14 cut: 4
Blockers backported this week: 9
Blockers we are still waiting on: 9
If there's anything else we should be waiting on, please make a proposal to add
it to the blocker board sooner rather than later (even if you're still
investigating...fix doesn't have to be fully ready yet, but do please update in
the ticket how it is progressing for anything taking "longer than a week")
On 3/5/21, 6:02 PM, "Owen Nichols" <onich...@vmware.com> wrote:
It's been three weeks since support/1.14 was cut. This week, backports for
12 blockers arrived on support/1.14. Great job!
As of now, the blocker board [1] shows that we are waiting on 9 blockers.
Once this list reaches zero, I can prepare RC1.
[1]
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12336052
On 2/26/21, 9:09 AM, "Owen Nichols" <onich...@vmware.com> wrote:
It's been two weeks since support/1.14 was cut, and the 1.14.0 blocker
board[1] still lists 5 issues (1 still Unassigned).
Given the lack of activity on GEODE-8943, GEODE-8860, and GEODE-8809,
should we defer them to 1.14.1 if we still "aim to ship on March 12th."?
On 2/18/21, 10:00 AM, "Owen Nichols" <onich...@vmware.com> wrote:
It's been about a week since support/1.14 was cut, and the 1.14.0
blocker board [1] still lists 5 issues (two of which appear to be Unassigned).
If a fix is taking longer than expected, please consider posting a status
update in the ticket about once a week, and ask for help on the dev list if you
need.
On 2/12/21, 1:20 AM, "Owen Nichols" <onich...@vmware.com> wrote:
support/1.14 has been cut. Any fixes on develop from today
onward should be marked as Fixed In 1.15.0.
The 1.14.0 blocker board [1] currently lists 5 issues. RC1
won't be created before this list gets to zero. To add to the blocker board,
please propose on the dev list.
On 2/10/21, 8:49 AM, "Owen Nichols" <onich...@vmware.com> wrote:
Sounds good.
Once cut, only fixes from the blocker board may be brought
to support/1.14.
After Feb 12, if you wish to add a critical issue to the
blocker board, please propose it on the dev list. If the community agrees it
is critical, you may tag it as "blocks-1.14.0"
Thanks,
Owen Nichols
1.14.0 Release Manager
On 2/9/21, 11:54 AM, "Alexander Murmann"
<amurm...@vmware.com> wrote:
Hi everyone,
We aren't seeing many issues that would prevent a
1.14.0 release on our blocker board <
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FDashboard.jspa%3FselectPageId%3D12336052&data=04%7C01%7Conichols%40vmware.com%7C71434b34031947faf13808d8e043eceb%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637505929646048174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rUwDSdZreJtJlnsFrAEPMpe4IajbLzSEunEjtNucJRc%3D&reserved=0>
and all issues have an owner. No new issues seem to be coming in either. This
seems like a good time to finally cut a 1.14 release branch and get us on track
to ship Apache Geode 1.14.0 in early March.
I propose we cut the branch at the end of this week and
aim to ship 4 weeks later, on March 12th.
