From: Josselin Poiret <dev@jpoiret.xyz>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: A Joyous Core-Updates Week-End 🎉
Date: Sat, 15 Apr 2023 09:59:20 +0200 [thread overview]
Message-ID: <87v8hxtw2v.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87fs9255b6.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Hi John,
John Kehayias <john.kehayias@protonmail.com> writes:
> Question on procedure: are we going to be posting every patch to guix-patches and waiting
> for QA to build? Or only for not trivial (whatever that means) patches? I guess I'm asking
> if this will be a sort of sprint weekend and larger changes/cleanup in the aftermath? This
> depends on context of course, but in light of recent discussions on patch pushing, QA, and
> teams (that I need to catch up on) I wanted to see what we were doing here.
Good question. My personal opinion on this is that fixes for
dependencies that impact multiple packages could be reviewed on the spot
while leaf packages could wait until later.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-04-15 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:16 A Joyous Core-Updates Week-End 🎉 Josselin Poiret
2023-04-12 9:55 ` Simon Tournier
2023-04-12 12:46 ` Maxim Cournoyer
2023-04-12 17:32 ` Status of Julia on core-updates (was Re: A Joyous Core-Updates Week-End 🎉) Simon Tournier
2023-04-12 17:56 ` Simon Tournier
2023-04-15 0:59 ` A Joyous Core-Updates Week-End 🎉 John Kehayias
2023-04-15 7:59 ` Josselin Poiret [this message]
2023-04-15 9:30 ` Andreas Enge
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=87v8hxtw2v.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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 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).