Hi Joao, all, Given we’re only now more available after the major 4.19 release to work on other releases, could we reconsider the timeline and come up with an updated plan.
I think we should target early March to give us some space to work on the issues and PRs. Joao - I’m assuming you still want to be RM for the release, have you triaged the current issues and PRs to identify the must haves and good to haves for 4.18.2 ? And anyone else have any must have issues and PRs they want in 4.18? Regards. Regards. ________________________________ From: João Jandre Paraquetti <j...@scclouds.com.br> Sent: Monday, December 11, 2023 6:18:34 PM To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: [PROPOSE] ACS 4.18.2.0 I think we can push a week or two earlier on the proposed schedule, it would look something like this: - From now till the final week of January (1.5 months): accept bug fixes and minor improvements - First week of February: accept only blocker and critical bug fixes, aiming to stabilize the branch. - Second week of February: start cutting RCs, vote and finish release work. What do you think? Best regards, João Jandre. On 12/9/23 17:22, Rohit Yadav wrote: > +1 > > Given, 4.18 branch is benefitting from maintenance work already, I wouldn't > mind if you want to push it earlier to even say end of Jan, and target > release in Feb 2024. > > > Regards. > > ________________________________ > From: João Jandre Paraquetti <j...@scclouds.com.br> > Sent: Friday, December 8, 2023 23:32 > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: [PROPOSE] ACS 4.18.2.0 > > Hi all, > > As suggested on the 4.20.0.0 discussion thread (see > https://lists.apache.org/thread/nyoddmwydz2t59hsfs7gf0vozlf7n434), I'd > like to propose the release of version 4.18.2.0 with myself as the RM, > here's a rough timeline: > > - From now till the second week of February (2 months): accept bug > fixes and minor improvements > - Third week of February: accept only blocker and critical bug fixes, > aiming to stabilize the branch. > - End of February: start cutting RCs, vote and finish release work. > > We currently have 7 open PRs [1] and 51 open issues [2] with 4.18.2.0 as > milestone, I believe the above timeline should give enough time to solve > all concerns. In case anyone wants to include a bug fix or a pull > request in 4.18.2.0 milestone, please mention me (JoaoJandre) on github. > > If anyone has any suggestions, please voice them. > > [1]: > https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.18.2.0+is%3Aopen > [2]: > https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.2.0 > > Best regards, > João Jandre > > > > >
