> > That said, I believe security updates are the most important to them so > > you could consider supporting the last release on EL6 a bit longer. I > > don't know how much of a time/effort difference that makes compared to > > supporting it longer on the newest release. > > Yeah, I can certainly try for a bit longer if it's useful to people, > though help doing the backports may be appreciated when we get there.
I think we are discussing two things which are different. Maintaining EL6 releases is one thing and we are not dropping that at all - we are sticking with our commitment. For those who need even longer support cycle there are 3rd party vendors like Red Hat. On the other hand, what Dominic suggest is dropping EL6 from the next release. That's a different story. And that's not that hot topic from user perspective, but plugins should be taken into consideration for sure. For discovery, I can say I am fine with dropping EL6 from the next release, but I can understand this is huge move and if there is a chance to postpone this one another release let's just do it. But I would like to see immediate planning and actions in order to achieve smooth exit phase. Can we identify first what needs to be done in order to drop EL6? Also can we do something for users to smoother the experience? Some web banners, blog posts? Perhaps a RFC can help here so it's recorded and visible for others. -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
