From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Timeline for Python 3.9 switch and Python 3.7 removal
Date: Fri, 19 Feb 2021 01:36:56 +0100 [thread overview]
Message-ID: <ee243ebcd48b0e77e3d89fdf37d75c4c6c446cee.camel@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr--14wwrRttdEO-TWM4FSMkFJcWR8gwaZ-=P=Pq1CUS5A@mail.gmail.com>
On Thu, 2021-02-18 at 16:01 -0800, Alec Warner wrote:
> On Thu, Feb 18, 2021 at 3:45 PM Michał Górny <mgorny@gentoo.org> wrote:
> >
> > Hi,
> >
> > I'd like to discuss a rough timeline for switching the default
> > PYTHON_TARGETS to python3.9.
> >
> > According to the upstream release schedule [1], the last bugfix release
> > is planned for May. Afterwards, upstream will release only security
> > fixes. At the same time, our rough current schedule [2] suggests that
> > we'll start last-riting stuff May 1st, so the 3.7 target would be
> > removed in 15-30 days.
> >
> > Do you think 2021-06-01 would be a reasonable planned switchover date?
>
> So you are saying we will start masking packages may 1st and we will
> drop 3.7 targets 30 days later (june 1?)
>
> (I felt like this was a bit ambiguous?)
The target will be removed when all packages not supporting 3.8 are
removed, so the exact time depends on what package will remain
in ::gentoo at May 1st.
Ideally, all packages will be ported by then and the only packages to
mask will be backports. For these, I use the shorter 14 day period.
However, if we have to remove some real packages I'll use 30 days
instead.
--
Best regards,
Michał Górny
prev parent reply other threads:[~2021-02-19 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 23:45 [gentoo-dev] [RFC] Timeline for Python 3.9 switch and Python 3.7 removal Michał Górny
2021-02-19 0:01 ` Alec Warner
2021-02-19 0:36 ` Michał Górny [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=ee243ebcd48b0e77e3d89fdf37d75c4c6c446cee.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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