From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: "Konrad Hinsen" <konrad.hinsen@fastmail.net>,
72840@debbugs.gnu.org,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Noé Lopez" <noe@xn--no-cja.eu>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
andreas@enge.fr
Subject: [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section.
Date: Wed, 02 Oct 2024 18:20:12 +0200 [thread overview]
Message-ID: <87y136v5mr.fsf_-_@gnu.org> (raw)
In-Reply-To: <CA+3U0ZkKOfj-WwjJnecB4Ue7R=_w0d08zFaX8SMHsfofQt7uzA@mail.gmail.com> (Greg Hogan's message of "Tue, 24 Sep 2024 12:32:53 -0400")
Greg Hogan <code@greghogan.com> skribis:
> On Mon, Sep 23, 2024 at 6:11 PM Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>> +If it has many dependent packages---as is the case for example with
>> +Python version@tie{}2---the relevant team must propose a deprecation
>> +removal agenda and seek consensus with other packagers for @b{at least
>> +one month}. It may also invite feedback from the broader user
>> +community, for example through a survey. Removal of all impacted
>> +packages may be gradual, spanning multiple months, to accommodate all
>> +use cases.
>> +
>> +When the package being removed is considered popular, whether or not it
>> +is a leaf, its deprecation must be announced as an entry in
>> +@code{etc/news.scm}.
>
> Hi Ludo',
>
> Is the intent for the news entry to pre-announce the removal of a
> popular package, as specified for other kinds of deprecation and
> removal?
What the paragraph above means is that a news entry is published when
the popular package is deprecated, which could be months before it is
removed.
Does that make sense?
Ludo’.
next prev parent reply other threads:[~2024-10-02 16:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 19:13 [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-02 11:53 ` [bug#72840] " pelzflorian (Florian Pelz)
2024-09-05 21:26 ` bug#72840: " Ludovic Courtès
2024-09-05 21:31 ` [bug#72840] [PATCH RFC v2] " Ludovic Courtès
2024-09-11 7:04 ` Maxim Cournoyer
2024-09-11 10:11 ` [bug#72840] [PATCH RFC v3] " Ludovic Courtès
2024-09-12 0:40 ` Maxim Cournoyer
2024-09-23 22:11 ` [bug#72840] [PATCH RFC v4] " Ludovic Courtès
2024-09-24 16:32 ` Greg Hogan
2024-09-25 8:47 ` Andreas Enge
2024-10-02 16:20 ` Ludovic Courtès [this message]
2024-09-11 10:11 ` [bug#72840] [PATCH RFC] DRAFT " Ludovic Courtès
2024-09-11 18:30 ` Noé Lopez via Guix-patches via
2024-09-13 17:23 ` Ludovic Courtès
2024-09-11 19:49 ` [bug#72840] Deprecation policy Konrad Hinsen
2024-09-13 17:32 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-15 8:22 ` Konrad Hinsen
[not found] ` <66e1e26e.050a0220.2c8e9.9533SMTPIN_ADDED_BROKEN@mx.google.com>
2024-09-12 15:39 ` Greg Hogan
2024-09-13 16:41 ` [bug#72839] Using RFC process? (was Re: [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section.) Simon Tournier
2024-09-13 17:38 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-13 18:11 ` [bug#72839] bug#72840: " Simon Tournier
2024-09-13 20:57 ` [bug#72840] " indieterminacy
2024-09-23 21:44 ` Ludovic Courtès
2024-09-17 12:21 ` [bug#72840] Orphaned packages Konrad Hinsen
2024-09-23 21:47 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-24 5:21 ` Konrad Hinsen
[not found] <87a5gbe9eh.fsf@inria.fr>
2024-09-14 7:14 ` Janneke Nieuwenhuizen
2024-09-26 13:16 ` Ludovic Courtès
[not found] <87zfowk9bh.fsf@gnu.org>
2024-09-23 22:16 ` 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=87y136v5mr.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=72840@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=code@greghogan.com \
--cc=konrad.hinsen@fastmail.net \
--cc=maxim.cournoyer@gmail.com \
--cc=noe@xn--no-cja.eu \
--cc=pelzflorian@pelzflorian.de \
/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).