From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>, "John Snow" <jsnow@redhat.com>
Subject: Re: Debian support lifetime (was Re: [PATCH] docker: move tests from python2 to python3)
Date: Tue, 24 Sep 2019 10:06:04 +0100 [thread overview]
Message-ID: <20190924090604.GB2106@redhat.com> (raw)
In-Reply-To: <20190924073513.GA2106@redhat.com>
On Tue, Sep 24, 2019 at 08:35:13AM +0100, Daniel P. Berrangé wrote:
> On Mon, Sep 23, 2019 at 04:05:33PM -0300, Eduardo Habkost wrote:
> > On Mon, Sep 23, 2019 at 01:19:41PM -0400, John Snow wrote:
> > > On 9/23/19 10:50 AM, Cleber Rosa wrote:
> > [...]
> > > >> diff --git a/tests/docker/dockerfiles/debian-xtensa-cross.docker b/tests/docker/dockerfiles/debian-xtensa-cross.docker
> > > >> index b9c2e2e531..e6f93f65ee 100644
> > > >> --- a/tests/docker/dockerfiles/debian-xtensa-cross.docker
> > > >> +++ b/tests/docker/dockerfiles/debian-xtensa-cross.docker
> > > >> @@ -18,7 +18,7 @@ RUN apt-get update && \
> > > >> flex \
> > > >> gettext \
> > > >> git \
> > > >> - python-minimal
> > > >> + python3-minimal
> > > >
> > > > I'm getting Python 3.5.3-1+deb9u1 here, so it LGTM.
> > > >
> > >
> > > Oh, that's actually a bit of a problem. I tested on 3.5+, but I think
> > > some people want 3.6+.
> > >
> > > I don't know much about Debian, but we either need to guarantee 3.6+ or
> > > backtrack our plans to 3.5+.
> >
> > Good catch. I forgot we were going to keep 3.5 support because
> > of Debian 9.
> >
> > Now, I'd like to clarify what the wording on our supported build
> > platforms documentation is supposed to mean for Debian.
> >
> > The document says:
> >
> > ] For distributions with frequent, short-lifetime releases, the project will
> > ] aim to support all versions that are not end of life by their respective
> > ] vendors. For the purposes of identifying supported software versions, the
> > ] project will look at Fedora, Ubuntu, and openSUSE distros. Other short-
> > ] lifetime distros will be assumed to ship similar software versions.
> > ]
> > ] For distributions with long-lifetime releases, the project will aim to support
> > ] the most recent major version at all times. Support for the previous major
> > ] version will be dropped 2 years after the new major version is released. For
> > ] the purposes of identifying supported software versions, the project will look
> > ] at RHEL, Debian, Ubuntu LTS, and SLES distros. Other long-lifetime distros will
> > ] be assumed to ship similar software versions.
> >
> > Debian 10 was released in July 2019. Are we really willing to
> > support Debian 9 as a supported build platform until July 2021?
> > The Debian Project itself won't support Debian 9 after July 2020.
>
> This is an oversight on my part - I didn't realize Debian releases
> were supported for such a short time in parallel.
>
> There should be a general statement that, no matter what else the
> policy states, we do *NOT* support any distro that has been end of
> life by its vendor.
>
> > Even for other long-lifetime distros, I really think "2 years
> > after the new major version is released" is too long, and I'd
> > like to shorten this to 1 year.
>
> I guess this is ok, since this. is still quite a long life time of
> support for distros. eg RHEL has a 3-4 year gap between major
> releases, that gives 4-5 years for each release being supported by
> QEMU. Other LTS distros are similar
Having said that, in the past we did have some pushback from people who
were staying on Ubuntu LTS releases for quite a long time, which influenced
the decision to have a 2 year overlap. In practice that hopefully isn't too
big a problem, as support for the other LTS distros probably means Ubuntu
LTS will work ok regardless for 2 releases.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-09-24 9:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 20:00 [PATCH] docker: move tests from python2 to python3 John Snow
2019-09-20 21:29 ` Eduardo Habkost
2019-09-23 14:50 ` Cleber Rosa
2019-09-23 14:57 ` Philippe Mathieu-Daudé
2019-09-23 15:19 ` Cleber Rosa
2019-09-23 17:19 ` John Snow
2019-09-23 19:05 ` Debian support lifetime (was Re: [PATCH] docker: move tests from python2 to python3) Eduardo Habkost
2019-09-23 21:32 ` John Snow
2019-09-24 7:35 ` Daniel P. Berrangé
2019-09-24 9:06 ` Daniel P. Berrangé [this message]
2019-09-25 20:04 ` Eduardo Habkost
2019-09-26 11:58 ` Daniel P. Berrangé
2019-09-26 12:18 ` Peter Maydell
2019-09-26 12:44 ` Daniel P. Berrangé
2019-09-26 17:43 ` John Snow
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=20190924090604.GB2106@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.