Tata, both 4.19 and 4.20 are stable releases. Of course 4.19 has undergone more stabilisation by now. There will be a 4.19.2 soon, and a 20.1 soon after that. Any bugs for now go onto both release branches. Stable releases have an end of life after which it is no longer guaranteed fixes go on these branches and obviously that moment comes sooner for 4.19 then for 4.20. We also plan to release a 21 this year and will branch it off main as we release. The new release will be for new features. If you don't need any features on newer branches you can stay on an older branch. We always try, and are generally successful at creating smooth upgrade paths. So in short, go for the last release of the release branch that contains the features you need and follow newer branches when, 1. the branch you are on is end of life, or 2. the newer branch contains a new feature that you need.
I hope this explains it. and yes, we hope for more documentation volunteers, to formulate it in our favour. regards, On Thu, Jan 30, 2025 at 1:39 AM Chi vediamo <tatay...@gmail.com> wrote: > Allow me to provide some background. > > Certainly we are testing right now Cloudstack agaist Openstack. Openstack > Which I know, and the Openstack documentation is "comparatively speaking" > fantastic -Yes they have the secret sauce hidden and other stuff. > > Granted: Openstack does not have a lot of response from the community as > Cloudstack - Cloudstack have way better response - some times ambiguos but > responsive. > > Now As many apache projects, you have the stable version and the > development version for those who want to try the absolute new, but is not > stable. > > Thew the Question is: > IS the scenario like > 4.19.3 is the stable for the 4.19.X > 4.20.0 is the stable for the 4.20.X > ?? > or the scenario is like > 4.19.X is the stable > 4.20.x Is the future release still in development. > ?? > > we just need to know what is the scenario here, as I for somer reason > though 4.20.X was the latest greates stable release. Not speaking about > features just stability. > > Is 4.19.3 the stable release or is the 4.20.0 > > I saw patches and RC for the 4.19.X. > > Thank you very much. > > Tata Y. > > > > > On Jan 27, 2025, at 8:26 AM, Daan Hoogland <daan.hoogl...@shapeblue.com> > wrote: > > > > Chi/Tata, there are different answers possible. > > I will not try to give you a project standpoint on this. > > > > As a company we usually recommend the latest dot release (i.e. not a .0 > but a .1/.2/.1.3 etc.) but also in the end make sure you test the subset of > functionality you will be using / exposing to your customers. If it hasn't > gone through your test environment it shouldn't go to your production site. > > > > regards, > > > > > > > > > > ________________________________ > > From: Chi vediamo <tatay...@gmail.com> > > Sent: 27 January 2025 14:10 > > To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> > > Cc: dev <dev@cloudstack.apache.org> > > Subject: Re: upcoming release 4.19.2 > > > > Can you tell us. Which release should be used for production ?? > > > > I was trying hardly the 4.20 and maybe that is the main problem in my > case? > > > > Tata Y > > > >> On Jan 27, 2025, at 8:01 AM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > >> > >> yes Ricardo, All fixes will be merged forward to the 4.20 and main > >> branches, provided these are still relevant. > >> > >>> On Mon, Jan 27, 2025 at 1:51 PM Ricardo Pertuz > >>> <ricardo.per...@kuasar.co.invalid> wrote: > >>> > >>> Out of curiosity, are these fixes included/merge in the following > 4.20.x > >>> release? > >>> > >>> > >>> Atte, > >>> > >>> Ricardo Pertuz > >>> > >>> > >>>> On 27 Jan 2025 at 6:58 AM -0500, Rohit Yadav < > rohit.ya...@shapeblue.com>, > >>>> wrote: > >>>> Hi Daan, > >>>> > >>>> Since we're already ready, why don't we cut RC1 sooner that way more > >>> people can test and if there any blocker/critical issues we can still > cut > >>> another RC? > >>>> > >>>> From what I've followed, the 4.19 branch has already 100s of > issues/PRs > >>> fixed and ready to create ship a release out of. > >>>> > >>>> > >>>> Regards. > >>>> > >>>> > >>>> > >>>> > >>>> ________________________________ > >>>> From: Daan Hoogland <daan.hoogl...@gmail.com> > >>>> Sent: Monday, January 27, 2025 17:01 > >>>> To: dev <dev@cloudstack.apache.org> > >>>> Cc: users <us...@cloudstack.apache.org> > >>>> Subject: upcoming release 4.19.2 > >>>> > >>>> LS, > >>>> > >>>> As stated in [1] I want to call a freeze on the 4.19 branch this > week. My > >>>> plan is still to create an RC by friday > >>>> > >>>> the current state is , > >>>> > >>>> - 125 closed PRs - > >>>> > >>> > https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.2+is%3Aclosed > >>>> - 39 open PRs and - > >>>> > >>> > https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.19.2 > >>>> - 89 open issues - > >>>> > >>> > https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.2 > >>>> > >>>> A lot of the open PRs relate to the open issues and none are marked as > >>>> BLOCKER or even Critical so far. Please make sure to escalate and > mention > >>>> on this thread any issues that may need more attention than they are > >>>> getting right now. > >>>> > >>>> [1] https://lists.apache.org/thread/83qdklb6czqjdck20bo93rg1qhhq7h7q > >>>> > >>>> regards, > >>>> > >>>> -- > >>>> Daan > >>> > >> > >> > >> -- > >> Daan > > -- Daan
