public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: A change to how calm expires packages
Date: Sat, 29 Jan 2022 15:19:34 +0000	[thread overview]
Message-ID: <7081dd4b-ce5f-a08a-06cb-c01e843219d8@dronecode.org.uk> (raw)
In-Reply-To: <84e66513-3b8f-9c77-4d60-6b816a9eea7c@dronecode.org.uk>

On 20/01/2022 14:33, Jon Turney wrote:
> 
> To try to avoid packages lingering in the 'test' status indefinitely 
> (which leads to them not being installed by most users, as they don't 
> run setup with 'consider test packages' enabled, thus these packages 
> generally aren't getting used, so having them isn't generating much 
> value), I'm planning to change how calm expires packages:
> 
> Currently (in the absence of configuration otherwise [1]), calm will 
> retain up to 3 non-test versions, and 3 test versions, and expire all 
> other versions.
> 
> I plan to change this to also expire test versions which are superseded 
> by a non-test version (that is: expire test versions where a non-test 
> version with a higher version number exists).
> 
> I believe this makes the default behaviour closer to what package 
> maintainers are likely to want to happen.

This change has been deployed.

      parent reply	other threads:[~2022-01-29 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 14:33 Jon Turney
2022-01-20 16:24 ` Ken Brown
2022-01-20 17:42 ` Achim Gratz
2022-01-21  7:27 ` Brian Inglis
2022-01-21 10:11 ` Hamish McIntyre-Bhatty
2022-01-29 15:19 ` Jon Turney [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=7081dd4b-ce5f-a08a-06cb-c01e843219d8@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).