From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [RFC][PATCH 1/1] ci: Ubuntu xenial -> bionic
Date: Fri, 18 Mar 2022 08:31:36 +0100 [thread overview]
Message-ID: <YjQ1WKtV0amHh4Aq@pevik> (raw)
In-Reply-To: <CAEemH2cB+k+dbS_N=S0jGs9H3ct1wBUYhuaR-+V7wRVtydVN_g@mail.gmail.com>
Hi Li, Cyril,
> Hi Petr,
> On Wed, Mar 16, 2022 at 11:08 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Tested
> > * bionic
> > https://github.com/pevik/ltp/actions/runs/1993375270
> > * focal
> > https://github.com/pevik/ltp/actions/runs/1993443143
> > And as I noted xenial still works. I wanted to avoid false positives when
> > repos
> > get down, but obviously we have 4 years time (ends in 01 Apr 2026).
> +1 for bionic. (we can do an upgrade to focal when bionic reach EOL)
> According to the release cycle page[1] of ubuntu ORG, the
> Xenial (16.04) version is being deprecated, which means
> no hardware and maintenance updates anymore. But we (LTP)
> still merging new features and regression testcases, I'm afraid
> that will bring some known failures in Xenial then to cost energy
> for debugging.
So you'd keep Xenial until the end of it's Extended Security Maintenance (ESM)
support in 2026? I'm not sure myself if it's a good idea to drop Xenial now and
solve these problems. Maybe we should hold this change for some time.
And if we upgrade to bionic, it would be good to finish a docs of supported
kernel/(g)libc/distro versions.
Kind regards,
Petr
> [1]https://ubuntu.com/about/release-cycle
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-18 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 15:04 [LTP] [RFC][PATCH 1/1] ci: Ubuntu xenial -> bionic Petr Vorel
2022-03-16 15:08 ` Petr Vorel
2022-03-18 6:14 ` Li Wang
2022-03-18 7:31 ` Petr Vorel [this message]
2022-03-18 7:43 ` Li Wang
2022-04-22 11:24 ` Petr Vorel
2022-05-27 12:07 ` Cyril Hrubis
2022-05-27 12:30 ` Petr Vorel
2022-05-27 12:50 ` Petr Vorel
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=YjQ1WKtV0amHh4Aq@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox