From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Merging the purge-python2-packages branch
Date: Wed, 01 Jun 2022 22:30:59 +0200 [thread overview]
Message-ID: <9ee43bfdcfdc7f6e0b2fa2318f2c9bc32a715701.camel@telenet.be> (raw)
In-Reply-To: <86zgiwi2le.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
zimoun schreef op wo 01-06-2022 om 21:51 [+0200]:
> Any user of Guix, scientist or not, can be surprised that their
> perfectly working packages are suddenly removed without a period of
> grace. Yes, these packages could have been removed before today since
> they are EOL since 2 years. It does not change my concern.
>
> What is the emergency in the maintenance burden that we cannot publicly
> announce the purge and wait a grace* period? For the broken packages, I
> understand. I am sorry but I am still missing for the perfectly working
> packages.
> [...]
> *grace period: it could have been short as couple of weeks.
The grace period has been started back in 2008 and ended in 2015.
I don't know the original location where this has been publicly
announced, but there is [0]:
> (from [0])
> Sunsetting Python 2
> [...]
> We did not want to hurt the people using Python 2. So, in 2008, we
> announced that we would sunset Python 2 in 2015,
This is a 5 year grace period, which is already a lot of weeks.
Futhermore, this has even been extended for five additional years:
> (from [0])
> and asked people to upgrade before then. Some did, but many did not.
> So, in 2014, we extended that sunset till 2020
So we're at a ten-year grace period. And some distros have informally
extended the grace period a bit longer to some limited degree.
That said, I suppose it would have been better to also repeat the
message about the grace period on the blog, channel news and info-guix
(and maybe on IRC too, why not) as you seem to suggest, for people that
follow distro news but not upstream news, given the large impact (many
python2 packages)?
[0]: https://www.python.org/doc/sunset-python-2/
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-01 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 13:25 Merging the purge-python2-packages branch Maxim Cournoyer
2022-05-30 15:18 ` zimoun
2022-05-30 15:32 ` Maxim Cournoyer
2022-05-30 16:49 ` zimoun
2022-05-31 7:39 ` Reza Housseini
2022-05-31 19:07 ` Maxim Cournoyer
2022-05-31 20:54 ` zimoun
2022-06-01 16:21 ` Ludovic Courtès
2022-06-01 19:51 ` zimoun
2022-06-01 20:30 ` Maxime Devos [this message]
2022-06-02 7:25 ` zimoun
2022-06-02 9:36 ` Maxime Devos
2022-06-02 14:04 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ee43bfdcfdc7f6e0b2fa2318f2c9bc32a715701.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).