Hi João, Glad to hear about your interests and I will fully support your effort to release manage the next major release 4.20.
In fact you can also help us with 4.18.2.0 maintenance release which will be relatively low-effort release and in doing so you can learn the logistics of release management and access to Github and CI/CD (including BO), learning how to update websites (project and docs) and pre/post release work on a low-effort basis. I like your proposed timeline, for 4.20, free by end of May, would allow 4-5 months of development work. And I think that would be beneficial for the community to have two major releases in a year, with 4.20 release in end ~H1 '24, possibly a 4.21 in end ~H2 '24. I've jotted my notes on becoming a release manager here, that could help you: https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+CloudStack+Release+Manager (I welcome any/all PMCs to review this) Recently, I had also written my thoughts on growing in the community generally: (again, PMCs are welcome to review this - for now these are just my thoughts) https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+Committer https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+How+to+Become+a+PMC+Member Regards. ________________________________ From: João Jandre Paraquetti <j...@scclouds.com.br> Sent: Wednesday, December 6, 2023 17:57 To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: 4.20 plans Hello all, We have quite a few new interesting features prepared for 4.20; there's the log4j PR, that we plan on merging as soon as 4.19 is released. We also have a few big PRs to be opened for 4.20: - Refactoring of the quota UI; - New feature to allow users to create custom UI themes and apply them to domains, user accounts, and internet DNS themes that are used to access the ACS MS; - Differential volume snapshots/backups for KVM; - And some more extensions that we are preparing here. Therefore, I'd like to propose myself as the release manager of 4.20.0.0, if none objects. I'd be guided by Daniel, who has recently been added to the PMC; any others who are willing to help would be welcome too. Here's the rough schedule I propose: - On the third week of May, we freeze the main branch. That means any feature must be in by the second week of May. Only accept critical/blocker issues until June. - As early as possible in June, cut 4.20.0.0 RC1 and further RCs if necessary, start/conclude vote, and finish release work. Best regards, João Jandre On 12/5/23 13:18, Daan Hoogland wrote: > devs, > > Other than we all have great new plans for integrations and other > features for 4.20 and we have about 300 issues to solve, There are > some platform issues that need addressing. So far I can think of > - the outstanding logging PR > - java 11 is out of support and we'll need to support a higher version > > I think we must address these as soon as we have a release. > Are there any other issues to address? >
