From: Eduardo Habkost <ehabkost@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Cleber Rosa" <crosa@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Deprecation policy and build dependencies
Date: Wed, 5 Jun 2019 17:49:20 -0300 [thread overview]
Message-ID: <20190605204920.GG22416@habkost.net> (raw)
In-Reply-To: <c6a830b7-2892-6f05-faa1-3c8124e7e78a@redhat.com>
On Wed, Jun 05, 2019 at 03:42:39PM -0500, Eric Blake wrote:
> On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>
> >> IOW, I don't think RHEL-7 support as a build platform blocks us from
> >> dropping py2. We merely need to tweak our build platforms doc to clarify
> >> our intent wrt add-on yum repos.
> >
> > If we clarify the docs in QEMU 4.1, is there anything that
> > prevents us from removing Python 2 support in QEMU 4.1 too?
>
> My take (but not definitive): if we have any CI setups that are testing
> RHEL 7 without software collections and/or EPEL, then save Python 2
> removal for 4.2 to give us time to update CI setups. But if all of our
> CI setups are already fine, and we clarify the docs, then I'm all for
> getting rid of Python 2 support in 4.1.
If we do this soon, CI system owners will have at least 9 weeks
to fix them before 4.1.0 is released.
>
> Similarly, if we are going to outlaw in-tree builds, let's get that done
> in 4.1 instead of waiting yet another release.
I'm missing the context on this. Is this from a separate discussion?
--
Eduardo
next prev parent reply other threads:[~2019-06-05 20:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 19:24 [Qemu-devel] Deprecation policy and build dependencies Eduardo Habkost
2019-05-31 22:06 ` John Snow
2019-06-03 12:26 ` Markus Armbruster
2019-06-03 18:02 ` John Snow
2019-06-03 18:16 ` Cornelia Huck
2019-06-03 19:44 ` Eduardo Habkost
2019-06-04 7:14 ` Philippe Mathieu-Daudé
2019-06-03 18:17 ` Peter Maydell
2019-06-03 18:21 ` John Snow
2019-06-03 18:27 ` Peter Maydell
2019-06-03 18:38 ` John Snow
2019-06-04 5:31 ` Markus Armbruster
2019-06-04 15:51 ` John Snow
2019-06-04 5:26 ` Gerd Hoffmann
2019-06-05 15:50 ` Daniel P. Berrangé
2019-06-05 20:13 ` Eduardo Habkost
2019-06-05 20:42 ` Eric Blake
2019-06-05 20:49 ` Eduardo Habkost [this message]
2019-06-05 22:02 ` Eric Blake
2019-06-06 5:22 ` Markus Armbruster
2019-06-06 9:19 ` Daniel P. Berrangé
2019-06-05 15:44 ` Daniel P. Berrangé
2019-06-05 18:13 ` Eduardo Habkost
2019-06-06 9:23 ` Daniel P. Berrangé
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=20190605204920.GG22416@habkost.net \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@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.