[foreman-dev] Re: adding VCR tests to hammer-cli

https://github.com/Katello/hammer-cli-csv/pull/116 Maybe this is right? On Fri, Jul 29, 2016 at 4:11 PM, Tom McKay wrote: > I'd like to add VCR tests to hammer-cli-csv[1]. The tests I have currently > run only against a live server. I was pointed to runcible as an

[foreman-dev] adding VCR tests to hammer-cli

I'd like to add VCR tests to hammer-cli-csv[1]. The tests I have currently run only against a live server. I was pointed to runcible as an example but am a bit overwhelmed by what I need to do in the time I have to do it. Has anyone done something similar already? Ideally I'd like to just be able

[foreman-dev] Pushed downstream translations to Transifex

This is a followup to the ConfigCamp discussion on translations. During the Satellite 6.2 release, Red Hat engaged a set of professional translators to localize the application. This was done in an internal instance of Zanata, and therefore not available to the community. During ConfigCamp we

[foreman-dev] From the demo - Plugin stats

Hi all, On yesterdays demo, Stephen asked if I'd share the plugin stats I've got, so here they are. Bear in mind that: * I've filtered out some things which are just dependency packages (eg .*deface.*) * I've merged the deb and rpm naming schemes into just "ruby..." * I have no visibility of the

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