Re: 4.20 plans
That's a great idea! I'll create a new thread to discuss 4.18.2.0. Best regards, João Jandre On 12/8/23 09:13, Wei ZHOU wrote: +1 I think it would be good to start as the RM of a minor release to better understand the role as a RM. Kind regards, Wei On Fri, 8 Dec 2023 at 11:55, Rohit Yadav wrote: 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 Sent: Wednesday, December 6, 2023 17:57 To: 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?
[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
Re: [VOTE] Adopt Github Discusssions as Users Forum
+1 Regards, Pearl Dsilva From: Rohit Yadav Sent: December 4, 2023 3:01 AM To: dev@cloudstack.apache.org ; priv...@cloudstack.apache.org Cc: us...@cloudstack.apache.org Subject: [VOTE] Adopt Github Discusssions as Users Forum All, Following the discussion thread on adopting Github Discussions as users forum [1], I put the following proposal for a vote: 1. Adopt and use Github Discussions as user forums. 2. The Github Discussions feature is tied with the us...@cloudstack.apache.org mailing list (PR: https://github.com/apache/cloudstack/pull/8274). 3. Any project governance and decision-making thread such as voting, releases etc. should continue to use the project mailing lists. Vote will be open for 120 hours (by Friday, 8th Dec). For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 Regards.
Re: [VOTE] Adopt Github Discusssions as Users Forum
+1 Cheers, Sven Vogel Apache CloudStack PMC member Am Freitag, den 12/08/2023 um 11:46 schrieb Suresh Kumar Anaparti: +1 Well organized platform, might also help to easily tag / track related issues, code and PRs in GitHub. Regards, Suresh On Thu, Dec 7, 2023 at 7:42 PM Nicolas Vazquez wrote: > > +1 (binding) > > Regards, > Nicolas Vazquez > > > From: Rohit Yadav > Date: Monday, 4 December 2023 at 05:01 > To: dev@cloudstack.apache.org , priv...@cloudstack.apache.org > Cc: us...@cloudstack.apache.org > Subject: [VOTE] Adopt Github Discusssions as Users Forum > All, > > Following the discussion thread on adopting Github Discussions as users forum [1], I put the following proposal for a vote: > > > 1. Adopt and use Github Discussions as user forums. > 2. The Github Discussions feature is tied with the us...@cloudstack.apache.org mailing list (PR: https://github.com/apache/cloudstack/pull/8274). > 3. Any project governance and decision-making thread such as voting, releases etc. should continue to use the project mailing lists. > > Vote will be open for 120 hours (by Friday, 8th Dec). > > For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 > > > Regards. > > > > >
Re: 4.20 plans
+1 I think it would be good to start as the RM of a minor release to better understand the role as a RM. Kind regards, Wei On Fri, 8 Dec 2023 at 11:55, Rohit Yadav wrote: > 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 > Sent: Wednesday, December 6, 2023 17:57 > To: 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? > > > > > >
Re: 4.20 plans
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 Sent: Wednesday, December 6, 2023 17:57 To: 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? >
Re: [VOTE] Adopt Github Discusssions as Users Forum
+1 Well organized platform, might also help to easily tag / track related issues, code and PRs in GitHub. Regards, Suresh On Thu, Dec 7, 2023 at 7:42 PM Nicolas Vazquez wrote: > > +1 (binding) > > Regards, > Nicolas Vazquez > > > From: Rohit Yadav > Date: Monday, 4 December 2023 at 05:01 > To: dev@cloudstack.apache.org , > priv...@cloudstack.apache.org > Cc: us...@cloudstack.apache.org > Subject: [VOTE] Adopt Github Discusssions as Users Forum > All, > > Following the discussion thread on adopting Github Discussions as users forum > [1], I put the following proposal for a vote: > > > 1. Adopt and use Github Discussions as user forums. > 2. The Github Discussions feature is tied with the > us...@cloudstack.apache.org mailing list (PR: > https://github.com/apache/cloudstack/pull/8274). > 3. Any project governance and decision-making thread such as voting, > releases etc. should continue to use the project mailing lists. > > Vote will be open for 120 hours (by Friday, 8th Dec). > > For sanity in tallying the vote, can PMC members please be sure to indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > [1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8 > > > Regards. > > > > >
