Howdy, I am not clear on what the shape of everything else is, but I think there are two larger updates that are in risk if we stick to our hard time based releases here:
1) Dynflow as a stand-alone service used by Foreman which is targeted for 1.16 GA but needs to also make 1.17 2) 1.17 with Rails 5.1 We've had a lot of packaging breakages which has prevented work on and subsequent testing of Rails 5.1 SCL for use in 1.17. Further, nightlies have been broken more than not which should lower confidence levels approaching a 1.17 branch date. I say this not to be an alarmist but to raise concerns such that we target a strong and stable release. Eric On Thu, Nov 16, 2017 at 6:58 AM, Ondrej Prazak <[email protected]> wrote: > Hi, > I am sending this just to let you know that, according to the schedule, > the 1.17 branching should happen in 2 weeks. > > O. > > -- > 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. > -- Eric D. Helms Red Hat Engineering -- 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.
