Re: [foreman-dev] Getting Foreman and Smart-Proxy to run in FIPS environment.

2017-11-23 Thread Dmitri Dolguikh
I added a bunch of (more) granular-level issues to http://projects.theforeman.org/issues/3511 tracker. Cheers, -d On Wed, Nov 22, 2017 at 2:13 PM, Dmitri Dolguikh wrote: > On Wed, Nov 22, 2017 at 9:33 AM, James Shewey wrote: > >> You may not be getting an ABRT because ruby was patched some tim

[foreman-dev] Discourse - next steps / actions

2017-11-23 Thread Greg Sutcliffe
Hi all, I'll try to keep this brief, at least by my standards :) Firstly, I think it's clear that the discussion is leaning towards implementing Discourse for at least one, and possibly both, of the mailing lists. Many people have contributed - I'd like to thank them all for keeping this from des

Re: [foreman-dev] 1.17 branching - status update

2017-11-23 Thread Lukas Zapletal
Thanks please announce the branching day a day ago and ask to stop merging breaking changes, so we can test our plugins with the "candidate" for branching. That would be super nice! LZ On Thu, Nov 23, 2017 at 2:03 PM, Ondrej Prazak wrote: > Hi, > this is just a quick summary of where we stand wi

[foreman-dev] 1.17 branching - status update

2017-11-23 Thread Ondrej Prazak
Hi, this is just a quick summary of where we stand with 1.17, please feel free to correct me if I got something wrong. foreman_selinux, smart-proxy, installer and modules have no blockers - at least none that we know of. Blockers for foreman are dynflow and Rails 5.1 as already stated previously