From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e@gmail.com>, guix-devel@gnu.org
Subject: Re: Layout of ‘define-configuration’ records
Date: Fri, 25 Nov 2022 10:18:00 -0500 [thread overview]
Message-ID: <87v8n3jc5z.fsf@gmail.com> (raw)
In-Reply-To: <861qpvdot1.fsf@gmail.com> (zimoun's message of "Tue, 22 Nov 2022 15:52:26 +0100")
Hi Simon,
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Maxim,
>
> On Mon, 21 Nov 2022 at 16:00, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> That sounds very appropriate indeed. I guess we could send
>> announcements on API breaking changes to both places. I suppose not
>> many people are registered to 'info-guix' (I wasn't myself until
>> recently ^^').
>
> Well, more is better here, no? :-)
>
>
>> I guess that's a question of how disruptive the API change is, but it'd
>> be convenient if it was 2 weeks to match the time the change might
>> appear on guix-patches un-reviewed.
>
> Well, the process for API change could be:
>
> 1. + submit to guix-patches,
> + in the same time, announce to guix-devel; so people not subscribed to
> guix-patches can chime.
> 2. + after 2 weeks, or consensus, merge the change,
> + in the same time, announce to guix-devel, info-guix and --news.
>
> There is no extra burden and it smooths the change for many users, IMHO.
>
> WDYT?
This sounds reasonable to me, with the addition that the "core" team
members should be added as CC when submitting the API changing patch(es)
(etc/teams.scm cc core).
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-11-25 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 3:47 [bug#58855] [PATCH 0/5] Update mcron to latest commit Maxim Cournoyer
2022-10-29 4:16 ` [bug#58855] [PATCH 1/5] services: configuration: Re-order generated record fields Maxim Cournoyer
2022-10-29 4:16 ` [bug#58855] [PATCH 2/5] services: mcron: Add log? and log-format fields to mcron-configuration Maxim Cournoyer
2022-10-29 4:16 ` [bug#58855] [PATCH 3/5] gnu: mcron: Use gexps and strip trailing #t Maxim Cournoyer
2022-10-29 4:16 ` [bug#58855] [PATCH 4/5] gnu: Remove guile2.2-mcron Maxim Cournoyer
2022-10-29 4:16 ` [bug#58855] [PATCH 5/5] gnu: mcron: Update to 1.2.1-0.5fd0ccd Maxim Cournoyer
2022-11-17 22:37 ` Layout of ‘define-configuration’ records Ludovic Courtès
2022-11-18 16:44 ` Maxim Cournoyer
2022-11-19 21:25 ` Katherine Cox-Buday
2022-11-20 13:47 ` Maxim Cournoyer
2022-11-21 10:26 ` Ludovic Courtès
2022-11-21 20:08 ` Maxim Cournoyer
2022-11-21 16:49 ` Katherine Cox-Buday
2022-11-21 21:00 ` Maxim Cournoyer
2022-11-22 14:52 ` zimoun
2022-11-25 15:18 ` Maxim Cournoyer [this message]
2022-11-21 10:22 ` Ludovic Courtès
2022-11-21 21:16 ` Maxim Cournoyer
2022-11-23 21:56 ` Ludovic Courtès
2022-11-25 15:15 ` Maxim Cournoyer
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=87v8n3jc5z.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.