public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Bonfire of the Packages
Date: Sun, 24 Sep 2023 22:13:37 +0200	[thread overview]
Message-ID: <5332985b-f48b-4968-88e4-6612b1b0856b@towo.net> (raw)
In-Reply-To: <ZRB+CP7vUxICeSMO@xps13>



Am 24.09.2023 um 20:20 schrieb gstrauss via Cygwin-apps:
> On Sun, Sep 24, 2023 at 01:32:59PM +0100, 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 what's needed is an automated process which removes unmaintained
>> packages, after some period of time in that state.
>>
>> I'm somewhat ambivalent about doing that, as they are probably of some use,
>> but on the hand I don't think our users are best served providing very old
>> packages with unknown numbers of bugs, security problems, etc., or which are
>> unsupported upstream.
> Were the first steps to be performed by an automated process, I would
> propose that the automated process mark and move packages
> 'pending delete' to a new category "abandoned", which is not installed
> by default, but selectable in the cygwin setup.exe.  Alternatively,
> 'promote' the abandoned packages to "testing".  After a period of time
> in "abandoned" or "testing", the packages could be removed to a holding
> area, but not yet deleted, since this is the time that some people might
> start to notice.  It would be nice to be able to restore packages
> relatively quickly during this period.  Finally, after another period of
> time passes, delete the package.
>
> Cheers, Glenn
I have two packages that were not updated for 7 years for a while, for 
different reasons, but are still maintained.
What criteria would you have in mind? I don't think this is a reasonable 
approach.
Thomas

  reply	other threads:[~2023-09-24 20:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 12:32 Jon Turney
2023-09-24 18:20 ` gs-cygwin.com
2023-09-24 20:13   ` Thomas Wolff [this message]
2024-03-24 14:07 ` Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages) Jon Turney
2024-03-24 17:31   ` 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

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=5332985b-f48b-4968-88e4-6612b1b0856b@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@cygwin.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).