GitHub user rohityadavcloud added a comment to the discussion: Define a release schedule for the project
Github Discussions isn't the right place to discuss project governance related matters, but may be used for discussions and to build initial consensus; it was enabled only as a platform to support user-forum interactions. If the intention is/was to only build consensus, then fine - but many PMCs and other stakeholders aren't on Github. Releases, project policy for changes, modernising codebase, I believe there they must be discussed on the dev@ ML. Personally, I think we've well-defined project bylaws and release process that works for me (and perhaps many of us) and I'm not very interested 'currently' to change them, but on convincing arguments I (and others) may participate and help support proposed changes. We generally target two major and two minor releases every year for the CloudStack project and sub-projects releases are on need-basis. However, even if a hard of doing X releases a year was there - who would drive them? And what happens if we miss, there is no way to ensure or enforce that. I appreciate the intentions but it's not practical to pull off. Nobody is stopping any PMC or committers to do a release, but releases cost time, energy and bandwidth, so many of cannot commit full-time on this to "ensure" they happen but only make our best attempt. I wouldn't consider O If you or Daniel or group of other people want to do more releases, go make it happen and update https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases GitHub link: https://github.com/apache/cloudstack/discussions/8970#discussioncomment-9747899 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
