Hi, > Then I'd open a PR with the switch from Rails 5.0 to 5.1 and > https://github.com/theforeman/foreman/pull/5026
After that one got merged, only https://github.com/theforeman/foreman/pull/4836 was the missing final change. > After that one got merged, core is using Rails 5.1 (and probably not > even Rails 5.0 compatible) and the RPM work can start. DEBs should just > work fine without modifications. > > Plugin authors should check if anything is missing for Rails 5.1 and > update, if needed. The final step to Rails 5.1 got just merged. > After that, the remaining deprecation notices with Rails 5.1 should get > fixed and once this is done, Rails 5.2 is probably already released. The remaining deprecation warnings with 5.1 can be found in config/as_deprecation_whitelist.yaml Regards -- Michael Moll -- 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 foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
