GitHub user weizhouapache added a comment to the discussion: Define a release schedule for the project
My 2 cents. Regarding major releases, we do have plan to create 2 major releases (1 LTS, 1 non-LTS) a year. However, it appears nobody is interested in the non-LTS release. Now all recent major releases are LTS releases. We do not have adequate resources to maintain multiple LTS releases and main branch. IMHO it is ok to have major LTS releases every 8-10 months. All new features should be public on cwiki several weeks before code freeze on, for instance https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.20+Design+Documents We could create minor releases more often, for instance every 2-3 months. I have suggested before. Regarding break changes, as many of you said, deprecate or announce in a LTS release, then remove or change in next LTS release. > 1. looking at our history, what would be the ideal cadence of major releases > for our context and why? > 2. how and when should we define the RM for each major? > 3. how should we introduce disruptive changes and remove compatibility? > 4. what are the community's common goals? > 5. regarding minor releases, should we flexibilize it more or be more rigid? > GitHub link: https://github.com/apache/cloudstack/discussions/8970#discussioncomment-9754595 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
