On Thu, Dec 14, 2017 at 6:08 PM, Ondrej Prazak <[email protected]> wrote:
> Hi, > quick summary about 1.17 branching status. The develop branch moved to > Rails 5 and turbolinks were added to tfm-ror51. Right now, the develop is > basically ready to move to Rails 5.1 by getting in [1]. When that is done, > there are packaging updates that need to be done - we need to update fog to > 1.42 [2] and move to higher version of Ruby scl. > > There are also other items planned 1.17: > > * dynflowd via foreman package [3], [4] - I assume these will go in after > the packaging changes > * broken UEFI provisioning, which was reported today [5] > > Given the rapidly approaching holidays and the fact that we are already > behind schedule, I would like to branch next week before people leave for > their vacations and not to postpone the branching until the next year. > Since Rails 5.1 is merged and that we are already mid vacation - is it safe to assume we can branch asap? (e.g. about a week from now) thanks! Ohad > > O. > > [1] https://github.com/theforeman/foreman/pull/4836 > [2] https://github.com/theforeman/foreman-packaging/pull/1975 > [3] https://github.com/theforeman/foreman-packaging/pull/1549 > [4] https://github.com/theforeman/foreman-packaging/pull/1959 > [5] http://projects.theforeman.org/issues/21975 > > -- > 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.
