Perhaps we could consider giving certain versions longer support cycles
then usual?
Not 2 years, but maybe instead of the usual 6 months make it 9 so that
users stuck because they can't upgrade to e.g. stretch yet won't be stuck
with a completely unmaintained version so quickly? Obviously only
On Thu, Jun 1, 2017 at 1:53 PM, 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
On Thu, May 18, 2017 at 10:57:03AM -0400, Stephen Benjamin wrote:
> On Wed, May 17, 2017 at 10:45 AM, Michael Moll wrote:
> > Hi,
> >
> > On Wed, May 17, 2017 at 03:11:12PM +0300, Tomer Brisker wrote:
> >> What do people think about dropping it in 1.16? This will still give
On Wed, May 17, 2017 at 10:45 AM, Michael Moll wrote:
> Hi,
>
> On Wed, May 17, 2017 at 03:11:12PM +0300, Tomer Brisker wrote:
>> What do people think about dropping it in 1.16? This will still give people
>> enough time to upgrade their systems as 1.15 will still be supported
On Wed, May 17, 2017 at 04:47:46PM +0200, Michael Moll wrote:
> Hi,
>
> On Wed, May 17, 2017 at 04:11:31PM +0300, Tomer Brisker wrote:
> > Is there some similar solution we can find for Debian so we don't hit the
> > same issue when we want to drop 2.1 eventually while still supporting
> >
Hi,
On Wed, May 17, 2017 at 04:11:31PM +0300, Tomer Brisker wrote:
> Is there some similar solution we can find for Debian so we don't hit the
> same issue when we want to drop 2.1 eventually while still supporting
> Jessie?
I can't think of a solution that's maintainable without requiring a
Hi,
On Wed, May 17, 2017 at 03:11:12PM +0300, Tomer Brisker wrote:
> What do people think about dropping it in 1.16? This will still give people
> enough time to upgrade their systems as 1.15 will still be supported for
> the next 6 months.
+1 on dropping 2.0 support for Foreman core.
--
Tomer Brisker writes:
> Hello,
>
> Ruby 2.0 has been EOL'ed over a year ago. More and more of our dependent
> libraries are dropping support for it, which means that we are either stuck
> with older versions or need to fix support in those libraries which may or
> may not be
Hi,
As a first step, I think about dropping it in Foreman core and its plugins,
since those have the largest dependencies and would be easiest to achieve.
I would be happy to also drop it in the proxy and the installer, but as
Eric mentioned, that would be more complex as we don't SCL those yet,
On Wed, May 17, 2017 at 8:19 AM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> On Wed, May 17, 2017 at 03:11:12PM +0300, Tomer Brisker wrote:
> > What do people think about dropping it in 1.16? This will still give
> people
> > enough time to upgrade their systems as 1.15
10 matches
Mail list logo