public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Updating CI-runners to buster
Date: Wed, 11 Mar 2020 14:51:13 +0100	[thread overview]
Message-ID: <20200311135113.k7pwrfe4uwjs3jx2@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200311123023.40c6eb0c@md1za8fc.ad001.siemens.net>

On Wed, Mar 11, 2020 at 12:30:23PM +0100, Henning Schild wrote:
> Seems you are just thinking about which combinations to actually test
> in CI. I think dropping stretch hosts from the official testing is no
> problem.
> You said "dropping stretch host support" which to me sounded like
> actually removing code or allowing code that means hosts will have to
> be >=buster.
> 
> Dropping tests is OK, dropping support is not. Of cause testing ensures
> support, but i would hope that the risk of a breakage is low.

If stretch host support is desired (which I second), then we should ensure that
patches breaking it don't go in (or are handled appropriately depending on the
host version) => we should continue testing stretch hosts.

I'll check what that means for the CI.

With kind regards,
Baurzhan.

      reply	other threads:[~2020-03-11 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14  6:01 vijai kumar
2020-02-17  6:07 ` Baurzhan Ismagulov
2020-02-18  6:10   ` vijai kumar
2020-02-24 14:16     ` Baurzhan Ismagulov
2020-02-24 15:09       ` vijai kumar
2020-03-10 13:59       ` Henning Schild
2020-03-10 17:54         ` Baurzhan Ismagulov
2020-03-11  8:28           ` Henning Schild
2020-03-11 10:37             ` Baurzhan Ismagulov
2020-03-11 11:30               ` Henning Schild
2020-03-11 13:51                 ` Baurzhan Ismagulov [this message]

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=20200311135113.k7pwrfe4uwjs3jx2@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox