public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-apps@cygwin.com, Marco Atzeri <marco.atzeri@gmail.com>
Subject: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Sun, 24 Mar 2024 14:07:22 +0000	[thread overview]
Message-ID: <68ee2d81-7716-4603-a889-3076e466ef5d@dronecode.org.uk> (raw)
In-Reply-To: <30524a03-4924-4aa0-9ebf-e5a0808226c2@dronecode.org.uk>

On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
> 
> Generally, we have a large number of old, unmaintained packages.
> 
> The policy [1] has always been "Packages without an active maintainer 
> may be pulled from the distribution.", but not actively enforced (in 
> fact prior to 2022, this used to say "are pulled", but I moderated the 
> statement, just to reflect reality).

I guess this needs to also mention upstream EOL status as a criteria.

[...]
> 
> Here's my personal list:
> 
> * python
> 
> After python27 (the last python2 version, which has been sun-setted 
> since 2020), both python36 and python37 should be removed (after 
> rebuilding any python-* package which don't currently provide 3.8, 3.9 
> versions)
  Marco,

I assume you are OK with the removal of python 3.5 (EOL Sept 2020) and 
3.6 (EOL Dec 2021)?

(I'm still dealing with cleaning up the final pieces of python27 
detritus, but these should hopefully be much smaller tasks)


  parent reply	other threads:[~2024-03-24 14:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 12:32 Bonfire of the Packages Jon Turney
2023-09-24 18:20 ` gs-cygwin.com
2023-09-24 20:13   ` Thomas Wolff
2024-03-24 14:07 ` Jon Turney [this message]
2024-03-24 17:31   ` Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages) Marco Atzeri
2024-03-24 17:46     ` Jon Turney
2024-03-24 18:51       ` Brian Inglis
2024-03-27 20:07         ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-04-18  6:01         ` Ake Rehnman
2024-04-19 12:16           ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-03-29 18:32         ` David Rothenberger
2024-03-30 15:25           ` Jon Turney
2024-04-01 17:16             ` David Rothenberger
2024-04-02 14:38               ` Jon Turney
2024-04-02 14:58                 ` Takashi Yano
2024-04-05 12:46                   ` Jon Turney
2024-04-05 23:17                     ` Takashi Yano
2024-04-01 15:22       ` Jon Turney
2024-03-27 21:18 Brian Inglis
2024-03-28 17:49 ` Jon Turney
2024-03-28 19:08   ` Brian Inglis

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=68ee2d81-7716-4603-a889-3076e466ef5d@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@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.
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).