Re: [foreman-dev] Deprecate EL6?

On Mon, Aug 08, 2016 at 06:34:01PM +0100, Greg Sutcliffe wrote: > On 8 August 2016 at 15:41, Ohad Levy wrote: > > > > On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms wrote: > > > >> This thread has seen a revival with many points being made on both sides. >

Re: [foreman-dev] Deprecate EL6?

On 8 August 2016 at 15:41, Ohad Levy wrote: > > On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms 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 >>

Re: [foreman-dev] Deprecate EL6?

On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms 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

Re: [foreman-dev] Deprecate EL6?

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

Re: [foreman-dev] Deprecate EL6?

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

Re: Re: Re: [foreman-dev] Deprecate EL6?

On 07/29, Dmitri Dolguikh wrote: > > The migration would be complicated for users who run TFTP/DHCP/DNS > > (etc..) on the same host. > > Why would it be complicated? Backup config files, restore them on the > new machine and run migrations. Sorry, I meant 'more complicated'. It's more

Re: Re: [foreman-dev] Deprecate EL6?

Katello provides full backup and restore scripts for users. We've not tested it for this specific case and or migrating a large infrastructure. Nor have we given guidance which are my bigger concerns. On Jul 29, 2016 6:57 AM, "Daniel Lobato Garcia" wrote: > On 07/29, Lukas

Re: [foreman-dev] Deprecate EL6?

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

Re: [foreman-dev] Deprecate EL6?

> > 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

Re: [foreman-dev] Deprecate EL6?

I’d like to see development of new features stopped on EL6: - no more random build breakages due to dependencies not supporting 1.8.7 and/or 1.9.3 - older releases are still available for those who prefer to stay on EL6 - Backup/restore procedures are documented, support for config file

Re: [foreman-dev] Deprecate EL6?

On Thursday 28 of July 2016 16:34:30 Greg Sutcliffe wrote: > So I had a read back through the thread, and drew a few conclusions. The > history seems to be: > > * The thread was opened ~10 weeks ago, and went quiet ~6 weeks ago > * At that time, there were 5 upvotes (Dominic, Daniel, Ewoud,

Re: [foreman-dev] Deprecate EL6?

On 28/07/16 13:08, Ewoud Kohl van Wijngaarden wrote: > On Thu, Jul 28, 2016 at 06:48:07AM -0400, Stephen Benjamin wrote: >> 2 users yesterday at the meet-up in DC specifically asked about this, and >> were rather surprised by the decision. They have some long-running instances >> of Foreman and

Re: [foreman-dev] Deprecate EL6?

On Tue, Jul 26, 2016 at 4:36 PM, Dominic Cleal wrote: > On 26/07/16 14:17, Ohad Levy wrote: > > +1 I believe 1.14 is a more suitable candidates. mostly after having a > > proper backup/restore procedure to migrate foreman, proxy and plugins. > > The manual already has a

Re: [foreman-dev] Deprecate EL6?

On 26/07/16 14:13, Eric D Helms wrote: > > > On Tue, Jul 26, 2016 at 4:46 AM, Dominic Cleal > wrote: > > On 10/05/16 10:26, Dominic Cleal wrote: > > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have > > the option of

Re: [foreman-dev] Deprecate EL6?

On Tue, Jul 26, 2016 at 4:13 PM, Eric D Helms wrote: > > > On Tue, Jul 26, 2016 at 4:46 AM, Dominic Cleal wrote: > >> On 10/05/16 10:26, Dominic Cleal wrote: >> > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have >> > the option of

Re: [foreman-dev] Deprecate EL6?

On Tue, Jul 26, 2016 at 4:46 AM, Dominic Cleal wrote: > On 10/05/16 10:26, Dominic Cleal wrote: > > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have > > the option of leaving it out of the 1.13 release. > > I've stopped nightly EL6 builds now and will

Re: [foreman-dev] Deprecate EL6?

On 10/05/16 10:26, Dominic Cleal wrote: > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have > the option of leaving it out of the 1.13 release. I've stopped nightly EL6 builds now and will remove the yum repos shortly too. -- Dominic Cleal domi...@cleal.org -- You received

Re: [foreman-dev] Deprecate EL6?

Hi, On Tue, May 10, 2016 at 10:26:42AM +0100, Dominic Cleal wrote: > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have > the option of leaving it out of the 1.13 release. This will be > documented in the 1.12 release notes. > > This would allow us to start dropping Ruby 1.8.7