On Thu, Jun 1, 2017 at 2:43 PM, Michael Moll <[email protected]> wrote:

> Hi,
>
> On Thu, Jun 01, 2017 at 01:53:40PM +0300, Tomer Brisker wrote:
> > Considering no objections were raised, as a first step I have opened a PR
> > to disable Ruby 2.0 tests for core & plugins:
> > https://github.com/theforeman/foreman-infra/pull/296
> >
> > I believe that 1.16 should require 2.1 at least
>
> +1
>
> > I hope that we could
> > figure out a way to get 1.17 to only support ruby 2.2.2 or newer so that
> we
> > can upgrade to rails 5.
>
> Regarding Rails 5, see Ohad's comment about Dominic's PR. I don't think
> 1.17 is ready to drop support for Ruby 2.1, as Debian 8 (jessie) support
> needs to be dropped with it, too. As Debian 9 (stretch) is about to be
> released in two weeks, I'd say people need more time migrate (although I
> know it's technically fine to release Foreman 1.16 as last release with
> support for both Debian releases).
>

My main concern here is that we would need to support 4.2 and 5 for a long
period of time without using any of the benefits in 5 (more work - less
features), what can be even worse, is that some of the bugs in rails will
be fixed only in 5 and then we would have some inconsistency across
distributions.

How much longer do you think we should announce in advance before
announcing that a given release is the last supported one for a given
distribution?

Ideally, I would like to try and minimize the blocking factors when
releasing a new feature (e.g. a nodejs or ruby version dependent feature).



>
> 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