Hi All, Happy New Year!
It's been about a month since the proposal, and we've fixed/tested/merged more than 140 Issues and PRs in the 4.16.1.0 milestone [1]. Currently, we've 45 open items in the 4.16.1.0 milestone, which are being tracked/triaged through the GitHub project 'CloudStack 4.16.1' [2]. We still have about 4 weeks for the soft freeze as proposed. Please continue your support on bug fixes, reviews, tests, etc. If you notice any issues in testing, please report here: https://github.com/apache/cloudstack/issues. Thank you. [1] https://github.com/apache/cloudstack/milestone/22 [2] https://github.com/orgs/apache/projects/24 Regards, Suresh On 17/12/21, 4:45 PM, "Suresh Anaparti" <suresh.anapa...@shapeblue.com> wrote: Hi All, I propose the following timelines for 4.16.1.0 release, which is targeted for Q1 2022. Please let me know if you have any feedback, thoughts. - (8 weeks) Ongoing - Mid-Feb 2022: Accept all bugs, issues, improvements allowed in LTS [1] - (1-2 weeks) Accept only critical/blocker fixes - (1 week) End-Feb 2022: Stabilise 4.16 branch, accept only blocker issues if any - End-Feb 2022 and Onwards: Cut 4.16.1.0 RC1 and further RCs if necessary, start/conclude vote, and finish release work You can find all the open issues and PRs at the 4.16.1.0 release milestone [2]. Ping me (@sureshanaparti) and Nicolas (@nvazquez) on your issues and PRs, that are to be included in 4.16.1.0. Looking forward for your support on bug fixes, reviews, tests, etc. Thanks. [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS [2] https://github.com/apache/cloudstack/milestone/22 Regards, Suresh From: Suresh Anaparti <suresh.anapa...@shapeblue.com> Date: Monday, 13 December 2021 at 6:39 PM To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org> Cc: "us...@cloudstack.apache.org" <us...@cloudstack.apache.org> Subject: [PROPOSE] RM for 4.16.1 Hi All, I'd like to put myself forward as the release manager for 4.16.1.0. My colleague Nicolas Vazquez will support me as the co-RM for the PR reviews/tests/merges, and others are welcome to support as well. I propose, we've a window of at least 8 weeks (2 months) to allow the community / users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline details by end of this week. I hope to have your support. Please let me know if you have any thoughts / comments. Regards, Suresh
