+1
On Tue, May 21, 2019, 13:43 Sven Vogel <s.vo...@ewerk.com> wrote: > +1 > > Von meinem iPhone gesendet > > > __ > > Sven Vogel > Teamlead Platform > > EWERK RZ GmbH > Brühl 24, D-04109 Leipzig > P +49 341 42649 - 11 > F +49 341 42649 - 18 > s.vo...@ewerk.com > www.ewerk.com > > Geschäftsführer: > Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer > Registergericht: Leipzig HRB 17023 > > Zertifiziert nach: > ISO/IEC 27001:2013 > DIN EN ISO 9001:2015 > DIN ISO/IEC 20000-1:2011 > > EWERK-Blog | LinkedIn | Xing | Twitter | Facebook > > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. > > Disclaimer Privacy: > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist > vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der > bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, > Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte > informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie > die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. > Vielen Dank. > > The contents of this e-mail (including any attachments) are confidential > and may be legally privileged. If you are not the intended recipient of > this e-mail, any disclosure, copying, distribution or use of its contents > is strictly prohibited, and you should please notify the sender immediately > and then delete it (including any attachments) from your system. Thank you. > > Am 21.05.2019 um 12:44 schrieb Boris Stoyanov < > boris.stoya...@shapeblue.com>: > > > > +1 > > > > —Bobby > > > > > > boris.stoya...@shapeblue.com > > www.shapeblue.com > > Amadeus House, Floral Street, London WC2E 9DPUK > > @shapeblue > > > > > > > >> On 21 May 2019, at 13:31, Wei ZHOU <ustcweiz...@gmail.com> wrote: > >> > >> +1 > >> > >> -Wei > >> > >> Rohit Yadav <rohit.ya...@shapeblue.com> 于2019年5月21日周二 上午11:40写道： > >> > >>> All, > >>> > >>> > >>> Thank you for your feedback and discussions. From what we've discussed > so > >>> far, we've lazy consensus that nobody wants to use el6 or are limited > to > >>> upgrade to el7/el8 due to potential risks. > >>> > >>> > >>> Moving forward I put forth the following for voting: > >>> > >>> > >>> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last > ones > >>> to support el6 packaging both for the management server and KVM host, > but > >>> users are discouraged from using them > >>> > >>> - Next major release (4.13.0.0) will document in its release notes that > >>> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. > 4.14 > >>> and onwards > >>> > >>> - After 4.13.0.0 is released, we will remove el6 related specs, > packaging > >>> scripts etc. from the codebase in the master branch > >>> > >>> > >>> [ ] +1 approve > >>> [ ] +0 no opinion > >>> [ ] -1 disapprove (and reason why) > >>> > >>> > >>> ** PMCs kindly add binding to your votes, thanks. > >>> > >>> > >>> Thanks. > >>> > >>> > >>> > >>> Regards, > >>> > >>> Rohit Yadav > >>> > >>> Software Architect, ShapeBlue > >>> > >>> https://www.shapeblue.com > >>> > >>> > >>> ________________________________ > >>> From: Erik Weber <terbol...@gmail.com> > >>> Sent: Wednesday, April 24, 2019 19:32 > >>> To: dev > >>> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14 > >>> > >>> CentOS7 was released 5 years ago, upgrading is long overdue anyway. > >>> Realistically the next CloudStack release won't be out the door for > >>> another ~4-6 months either. > >>> > >>> -- > >>> Erik > >>> > >>> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler > >>> <rwhee...@artifact-software.com> wrote: > >>>> > >>>> According to https://en.wikipedia.org/wiki/CentOS > >>>> > >>>> CentOS 6 EOL is 2020 > >>>> CentOS 7 EOL is 2024 > >>>> > >>>> > >>>> +1 for removing support for CentOS 6. > >>>> > >>>> As Erik pointed out the sites running CentOS6 will have to move soon > in > >>>> any event and it is probably better to do it now when there is still a > >>>> lot of current expertise and information available about how to do it > >>>> and how to make any changes to applications. > >>>> > >>>> Upgrading in a project that is under your control is usually easier > than > >>>> one forced on you by a security issue or an operational failure. > >>>> > >>>> Ron > >>>> > >>>>> On 4/24/19 3:24 AM, Erik Weber wrote: > >>>>> As an operations guy I can understand the want for future updates and > >>>>> not upgrading, but with the release plan of RHEL/CentOS I don't find > >>>>> it feasible. > >>>>> > >>>>> RHEL6 is 8 years old (and is still running kernel 2.6!) and isn't > >>>>> scheduled to be fully EOL until 2024. > >>>>> > >>>>> It is true that upgrading requires some effort (and risk) from > >>>>> operators, but this is work they eventually have to do anyway, so > it's > >>>>> not a matter of /if/ they have to do it, but rather when. > >>>>> > >>>>> It is also true that current CloudStack releases should continue to > >>>>> work, it's also possible that someone might back port future fixes to > >>>>> a RHEL6 compatible fork (you're more than welcome to). > >>>>> > >>>>> I'd vote +1 to remove support for el6 packaging. > >>>>> > >>> > >>> rohit.ya...@shapeblue.com > >>> www.shapeblue.com > >>> Amadeus House, Floral Street, London WC2E 9DPUK > >>> @shapeblue > >>> > >>> > >>> > >>> > > >
