From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrangé" <berrange@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, "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: Wed, 25 Sep 2019 17:04:40 -0300 [thread overview]
Message-ID: <20190925200440.GO8144@habkost.net> (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:
[...]
> > 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
Do you mean the 2 years period is OK (and shouldn't be changed),
or that shortening it to 1 year is OK?
--
Eduardo
next prev parent reply other threads:[~2019-09-25 20:06 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 [this message]
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=20190925200440.GO8144@habkost.net \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@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.