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 <opra...@redhat.com> wrote: > 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 > [1]. I tried to get in touch with the person who opened a PR to fix > turbolinks [2], but I got no response, so I opened a PR directly against > turbolinks [3]. foreman-task needs to get rid of alias_method_chain [4] and > katello needs to update accordingly [5]. > > > O. > > [1] https://groups.google.com/forum/#!topic/foreman-dev/3G9GuQ6d8ms > [2] https://github.com/dobtco/turbolinks-classic/pull/1 > [3] https://github.com/turbolinks/turbolinks-classic/pull/679 > [4] https://github.com/theforeman/foreman-tasks/pull/300 > [5] https://github.com/Katello/katello/pull/7083 > > -- > 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. -- Later, Lukas @lzap Zapletal -- 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.
