Thanks for the weekly updates! Do you forsee 1.17 working as:
1) Wait till the core codebase is updated to Rails 5.1 then branch and notify plugins 2) Branch soon at some stable point and backport the Rails 5.1 code changes I believe also on the list of items is the update to fog 1.42 that has a pending PR given the current version of Fog requires JSON < 2 and Ruby 2.4 comes with JSON 2+. On Dec 7, 2017 7:02 AM, "Ondrej Prazak" <[email protected]> wrote: > Hi, > this is a quick summary of current 1.17 branching status. As before, feel > free to correct/complete the information below. > > The new version of turbolinks-classic (2.5.4) was released about 12 hours > ago, and we work on adding it to tfm-ror51 [1]. > > Dynflowd deployment on Debian is almost ready to be merged [2]. > > OAuth fix for Rails 5 [3] did not receive much attention from OAuth > maintainers. We plan to package a forked version with included fix until > new gem version compatible with Rails 5 is released. > > The plan is to move slowly forward with Rails 5.0 [4], then introduce > incompatible changes to Rails 4.2 and move to 5.1 > > O. > > [1] https://github.com/theforeman/tfm-ror51-packaging/pulls > [2] https://github.com/theforeman/foreman-packaging/pull/1959 > [3] https://github.com/oauth-xx/oauth-ruby/pull/150 > [4] https://github.com/theforeman/foreman/pull/4867 > > -- > 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. > -- 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.
