Hi Wido On 01/10/2016 08:23 PM, Wido den Hollander wrote: > I personally am against LTS versions. If we keep the release cycle short > enough each .1 increment in version will only include a very small set > of features and bug fixes. > > In the old days it took months for a release, if we bring that back to > weeks the amount of changes are minimal.
The current release process is fine! We don't want to change that! No way! It fits the needs of those CloudStack users who want features fast and a minimal of risk. > You can then decide to always stay behind 3 months on the releases or > suddenly make a jump if you want to. No, unfortunately some of the users can not do that (yet). Staying 3 months behind fixes (security?) is not an option. In my case it would be even longer 6-12 months. For those, an _additinoal_ LTS version would be the way to go. > In my perspective clouds are agile and they should be developed that way. I fully agree with development, development could go even more agile, releases can be agile as well, the problems come when the applications go into operation. If the operation is not ready for deploying agile, those users will left behind. The only thing we need to do is backport fixes to a separate LTS branch. That's it. Only fixes, obvious fixes. > We should however simplify the upgrade even more: > - Separate database changes from code changes (proposed already) > - Put the VR in a separate project Yes, all fine with that. Again. I do not want to slow down development and releases. An additional LTS version could even help agile development because you can always rely on the argument: If you want most annoying stable cloudstack, use LTS. If you want to get features fast, use mainline. This is the trade off.
