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

I would like to bring one issue into attention for 1.17 https://github.com/theforeman/foreman-packaging/pull/1549#issuecomment-350983953 This was one of the mistakes we did in 1.16, where we removed some code from foreman-tasks that was supposed to be moved to the core, but it was not resolved

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

On Thu, Dec 07, 2017 at 01:02:00PM +0100, Ondrej Prazak wrote: 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. [3]

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

On Thu, Dec 07, 2017 at 09:52:21AM -0500, Eric D Helms wrote: Thanks for the weekly updates! I'll echo that. Greatly appreciated. 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

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

I would rather go with option 1 to avoid a large amount of cherry-picks. Thanks for pointing out the fog update. On Thu, Dec 7, 2017 at 3:52 PM, Eric D Helms wrote: > Thanks for the weekly updates! > > Do you forsee 1.17 working as: > > 1) Wait till the core codebase is

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

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

[foreman-dev] 1.17 branching - status update 3

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