On 07/21/2015 06:01 PM, Somesh Naidu wrote: > +1 > > Reasons: > 1. Technically speaking, Apache Cloudstack never had version less than 4.0. > But even if they are considered they would be EOL'd at some point. > 2. At some point the feature set disparity between version will make it > really complex to have direct upgrade paths. > 3. As Daan mentioned, 2.x and 3.x users can still upgrade to 4.6+ using a > multi-step approach (upgrading to 4.3/4.5 first). >
+1 I agree. Imho prior to 4.0 isn't really something we want to support. Upgrade to 4.0 first and then go to a ACS release. Wido > Regards, > Somesh > > -----Original Message----- > From: Erik Weber [mailto:terbol...@gmail.com] > Sent: Monday, July 20, 2015 2:30 PM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL] drop old upgrade code > > As a user, I'd say +1. > > I understand the concerns, but as long as there is a workaround I'm fine > with it. > > Would be great though if the upgrade scripts abort if it notices an upgrade > from an unsupported versions. > > Erik > > > Den mandag 20. juli 2015 skrev Daan Hoogland <daan.hoogl...@gmail.com> > følgende: > >> LS, >> >> In coverity the only remaining high impact issues are concerned with >> upgrade code. Some of it is in 4.3 and 4.5 code but most in pre-4 >> upgrades. >> >> I addressed the file Upgrade218to22.java in a PR [1] and I move that >> we don't pull it but instead drop the file altogether together with >> all upgrade code dating prior to 4.0.0. anybody on older versions can >> still upgrade to any version between 4.0 and 4.5 and move on from >> there. >> >> My objective is to have no high impact issues remaining so we clearly >> see when we are digressing beit by hand or in an automated way. >> >> +1? >> >> [1] https://github.com/apache/cloudstack/pull/603 >> -- >> Daan >>
