From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Cc: 63459@debbugs.gnu.org
Subject: Changes to the branching/commit policy
Date: Thu, 08 Jun 2023 15:24:37 +0100 [thread overview]
Message-ID: <87y1kuyqew.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Hey!
The changes in #63459 have strayed now in to touching the commit policy
[1]. My intent was to simplify the guidance by grouping it better, but I
think the significant change here is that the commit policy now
references the entire branching strategy, rather than just talking about
sending patches for review.
1: https://guix.gnu.org/manual/devel/en/html_node/Commit-Access.html#Commit-Policy
That new branching strategy makes some "should" requirements on sending
patches for review and pushing to topic branches for larger changes. It
also makes a "must" requirement on opening guix-patches issues to track
and manage merging branches.
I'd like to merge these changes next week since they've been up for a
few weeks, so do comment if you have any thoughts or if you'd like more
time to review them.
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next reply other threads:[~2023-06-08 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 14:24 Christopher Baines [this message]
2023-06-09 10:10 ` [bug#63459] Changes to the branching/commit policy Andreas Enge
2023-06-11 9:37 ` Christopher Baines
2023-06-11 9:53 ` Andreas Enge
2023-06-12 1:28 ` [bug#63459] " Maxim Cournoyer
2023-06-12 20:23 ` Christopher Baines
2023-06-17 5:22 ` John Kehayias
2023-06-17 9:57 ` Christopher Baines
2023-06-19 18:39 ` John Kehayias
2023-06-20 3:52 ` Christopher Baines
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=87y1kuyqew.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63459@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
/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).