From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, poky@yoctoproject.org
Subject: Re: [PATCH] poky.conf: prune SANITY_TESTED_DISTROS
Date: Wed, 08 Feb 2017 14:49:10 +0000 [thread overview]
Message-ID: <1486565350.3754.19.camel@linux.intel.com> (raw)
In-Reply-To: <01cb82a0-b38a-f56f-cbf9-da212ba4c4a5@gmail.com>
On Thu, 2017-01-26 at 17:35 -0800, Khem Raj wrote:
>
> On 1/24/17 7:04 AM, Tom Rini wrote:
> > On Tue, Jan 24, 2017 at 01:04:13PM +0000, Joshua Lock wrote:
> > > Remove several old/untested distros from the list:
> > > * poky-1.8 and poky-2.0 are no longer supported releases
> > > * ubuntu-14.04 is an LTS but we plan to remove it from the
> > > project's autobuilder cluster as the kernel is old and
> > > it doesn't use systemd -- therefore this will no longer
> > > be tested.
> >
> > Can you elaborate a bit more on the pain involved with supporting
> > Ubuntu
> > 14.04? Or, do you expect to drop Ubuntu 16.04 in favour of 18.04
> > at
> > around this point in 2019 and continue only supporting the latest
> > LTS
> > for Ubuntu? I ask because supported hosts are an important part of
> > companies being able to plan their use and upgrade
> > strategies. Thanks!
> >
>
> ubuntu 14.04 is still not EOL until April 2019, and I think lot of
> folks
> will keep using it until its EOLed, so it would be preferable to keep
> it
> as a supported host.
I agree that it would be preferable.
Unfortunately we don't currently have the resources to validate it so,
whilst we won't explicitly *not* support it, we can't include it in
SANITY_TESTED_DISTROS because it won't be tested by the YP QA team.
Regards,
Joshua
next prev parent reply other threads:[~2017-02-08 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 13:04 [PATCH] poky.conf: prune SANITY_TESTED_DISTROS Joshua Lock
2017-01-24 15:04 ` Tom Rini
[not found] ` <1485344411.4626.8.camel@intel.com>
2017-01-25 12:25 ` Tom Rini
[not found] ` <1486565201.3754.17.camel@intel.com>
2017-02-08 19:50 ` Tom Rini
2017-01-27 1:35 ` Khem Raj
2017-02-08 14:49 ` Joshua Lock [this message]
2017-01-25 8:35 ` Peter Kjellerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1486565350.3754.19.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.