agree. Moreover, we should try to avoid the new upgrade path for 4.xx.2 release.
-Wei On Friday, March 8, 2024, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > I think it would be most likely that we work towards releasing 4.19.1 > before 4.20.0. Then, it would be sensible to have 4.19.0 -> 4.19.1 -> > 4.20.0 upgrade path. > > > Regards. > > > > > ________________________________ > From: Daan Hoogland <daan.hoogl...@gmail.com> > Sent: Friday, March 8, 2024 14:50 > To: dev <dev@cloudstack.apache.org> > Subject: [PROPOSE] upgrade paths for 4.19 and 20 > > devs, > currently we have an upgrade path for 4.19.0.0 to 4.19.1.0 in the 4.19 > branch > in the main branch we have a 4.19.0.0 to (4.)20.0.0 upgrade path > merging fails because of this and allowing either or both in main will > cause main to fail (at least after upgrading) > If we are sure that 4.19.1 will be release and will be released before > 20 we can move the main upgrade path to be from 4.19.1 to 20 (never > mind the 4. or not) > If we do not release a 4.19.1 (first) we will have to move the path > back to originate from 4.19.0 > > Is this a sane strategy for now? > > If no-one objects I'll do the forward merge after the weekend. > > > -- > Daan >
