On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms <ericdhe...@gmail.com> wrote:
> This thread has seen a revival with many points being made on both sides. > However, things have gone cold for nearly a week now and there are > processes and decisions that hinge on the outcome with respect to users and > developers alike. Are we to assume that what has been done is done and this > discussion is moot? Some finality in this matter would be greatly > appreciated to either continue forward with EL6 builds and preparing all of > our ecosystem users for the 1.14 release to migrate or beginning now to > tell users they are SOL and to start testing transition and migration while > we work out and test the best way for them to do so. > I strongly prefer deprecating EL6 with Foreman 1.14, and would ask to revert the el6 changes in nighties. Ohad > > > Eric > > On Tue, Aug 2, 2016 at 1:15 PM, Justin Sherrill <jsher...@redhat.com> > wrote: > >> On 07/29/2016 05:29 AM, Michael Moll wrote: >> > Hi, >> > >> > On Fri, Jul 29, 2016 at 08:35:36AM +0100, Dmitri Dolguikh wrote: >> >> I have at least one feature planned for smart-proxy that requires >> >> dependencies not available on 1.8.7 (at all). At this point converting >> >> the smart-proxy to use SCL isn’t worth it, and it would be great not >> >> to have an additional 3-months wait. >> > >> > That would be exactly my point also, as I said in my mail for the >> > original discussion back then: If the support for EL6 is prolonged, the >> > proxy (and maybe even the installer) should really get into SCL, which >> > is definitely too much work for just 3 or 6 months. If EL6 support is >> > really needed, somebody[tm] needs to do that work, but then we could >> > also extend the lifespan not only some months, but probably some years. >> > >> > As I don't use RH based distro at the moment, I can't really say how >> > widespread the use of EL6 for Foreman really is... >> >> It seems surprisingly prevalent in katello users (maybe 30% from my >> instances helping users). >> >> Since there wasn't a clear statement of when the deprecation was going >> to occur (the original email thread was left without a conclusion), and >> the release notes for 1.11 did not say which future release would remove >> el6 support (until it was recently updated) I would vote to keep it for >> 1.13 and make it very clear to both users and devs. It would allow us >> (and users on el6) to more thoroughly test our backup and restore >> procedures across all plugins. >> >> >> >> > >> > Regards >> > >> >> -- >> 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 foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Eric D. Helms > Red Hat Engineering > Ph.D. Student - North Carolina State University > > -- > 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 foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
