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 during the 1.16 release process. As a result, we have
been blocked on releasing new tasks on 1.16 for several months
and we in fact have now newer version of remote execution in 1.15 than in
1.16.

Therefore I think this needs to be resolved before we start branching, to
avoid
this situation to continue forward in 1.17

-- Ivan

On Sat, Dec 9, 2017 at 5:11 PM, Michael Moll <[email protected]> wrote:

> Hi,
>
> On Sat, Dec 09, 2017 at 05:05:37PM +0100, Ewoud Kohl van Wijngaarden wrote:
> > 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] https://github.com/oauth-xx/oauth-ruby/pull/150
> >
> > The PR has been merged and version 0.5.4 has been released. Looks like we
> > should test with this.
>
> Debian nightlies' systest indeed is green again now.
>
> 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 [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.

Reply via email to