Hi, On Thu, Jun 01, 2017 at 02:49:12PM +0300, Ohad Levy wrote: > 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.
I didn't say it's going to be fun... ;) > 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'd like to see Ruby 2.1 supported until 1.17. While requiring newer nodejs versions isn't a problem thanks to the nodesource repositories, there's nothing similar for newer Ruby versions. However, if Rails 5 is really high priority, yes, then there's no way around getting rid of Ruby 2.1 after the 1.16 release and we should announce that as early as possible. I'm just seeing quite some users stuck with 1.16 on Debian 8 then - like some are still on 1.12/1.13 because of EL6. 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.
