public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] ci/ubuntu: impish -> jammy
Date: Mon, 20 Jun 2022 11:30:20 +0200	[thread overview]
Message-ID: <YrA+LFaA664fHpZA@yuki> (raw)
In-Reply-To: <20220617131659.27868-1-pvorel@suse.cz>

Hi!
> Ubuntu 21.10 impish EOL in 2027-04 (next month).
                                ^
			     2022-06
> Replace it with the latest stable release (EOL 2027-04).

Other than that:

Reviewed-by: Cyril Hrubis <chrubis@suse.cz>


> Reported-by: Andrea Cervesato <andrea.cervesato@suse.com>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi,
> 
> It's also a question whether use 20.04 LTS focal instead of 18.04 LTS
> bionic. I guess we'd like to cover everything: bleeding edge, used
> distros and very old and still used distros. bionic EOL next year
> (2023-04).

I would keep that till the EOL

> Kind regards,
> Petr
> 
>  .github/workflows/ci.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
> index fe28e4d05..a412f8904 100644
> --- a/.github/workflows/ci.yml
> +++ b/.github/workflows/ci.yml
> @@ -93,7 +93,7 @@ jobs:
>                CC: clang
>                METADATA: asciidoctor-pdf
>  
> -          - container: "ubuntu:impish"
> +          - container: "ubuntu:jammy"
>              env:
>                CC: gcc
>                METADATA: asciidoctor
> -- 
> 2.36.1
> 
> 
> -- 
> Mailing list info: https://lists.linux.it/listinfo/ltp

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2022-06-20  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 13:16 [LTP] [PATCH 1/1] ci/ubuntu: impish -> jammy Petr Vorel
2022-06-17 13:31 ` Petr Vorel
2022-06-20  9:30 ` Cyril Hrubis [this message]
2022-07-07 13:03   ` 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=YrA+LFaA664fHpZA@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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