From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Debian support lifetime (was Re: [PATCH] docker: move tests from python2 to python3)
Date: Thu, 26 Sep 2019 13:44:59 +0100 [thread overview]
Message-ID: <20190926124459.GA19660@redhat.com> (raw)
In-Reply-To: <CAFEAcA8Jn=er6mRZX+EYTePruTcHpLzVpqpydkERMVA9DdUOag@mail.gmail.com>
On Thu, Sep 26, 2019 at 01:18:35PM +0100, Peter Maydell wrote:
> On Thu, 26 Sep 2019 at 12:58, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > When first wording the lifetimes, I tried to strike a balance between
> > limiting what we have to support, while also not negatively impacting
> > a large number of QEMU developers or users. Since we had never had
> > such support lifetimes declared for QEMU before, I was fairly generous,
> > hence picking the 2 year overlap for LTS distros (Ubuntu, RHEL and
> > SLES).
> >
> > It is easier to come to a decision when considering a real world tech
> > problem related to the lifetime.
> >
> > The start of this thread was debating Debian / Python support. If we
> > fix the doc to put debian under the short life distro category, we'll
> > have solved the Python problem IIUC.
>
> I don't think Debian counts as a distro "with frequent, short-lifetime
> releases", though.
It is kind of in the middle ground between the short 6 month frequency
releases, and the long 3+ year major releases
> Stating overall that we don't intend to support distro versions
> that the distro themselves doesn't support ought to be sufficient,
> shouldn't it?
Yeah, that at least addresses the python question.
> In general, my view is that if we bump up against any of these
> support-lifetime limits then we're being too eager to drop
> support for something from QEMU and we should prefer to retain
> support for a while longer. I like and think that it's important
> that QEMU as a project does not live on the bleeding-edge and
> require latest-and-greatest versions of its dependencies to build.
Yeah, there's certainly a balance to be hit. If we only rarely have
to debate problems with desired min versions vs distros, and users
rarely complain that we're dropping stuff too soon, then that's a
sign we've got the balance about right.
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-26 12:47 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é
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é [this message]
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=20190926124459.GA19660@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).