From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
guix-maintainers@gnu.org, Marius Bakke <marius@gnu.org>
Subject: Re: Release progress, week 1
Date: Thu, 13 Oct 2022 18:33:36 +0300 [thread overview]
Message-ID: <Y0gv0K4IexunvRx/@3900XT> (raw)
In-Reply-To: <874jw7oinf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]
On Thu, Oct 13, 2022 at 05:19:48PM +0200, Ludovic Courtès wrote:
> Hello!
>
> Release progress: week 1.
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
> > Here’s a list of things to do to get there:
> >
> > • Merge ‘staging’ (?). What’s the status of that one, it seemed ready
> > a couple of weeks ago, but then I lost track of it. Marius?
>
> Marius, any update?
There's a commit by mhw I'd like to get in, it causes a rebuild of the
rust bootstrap but makes it take far less resources to build.
> Chris, does data.guix.gnu.org have enough info to provide insights?
>
> > • Get base binaries on all supported architectures in a timely
> > fashion, or drop some of the architectures.
>
> There was progress on i686-linux since last week:
>
> https://issues.guix.gnu.org/58366
> https://issues.guix.gnu.org/58352
>
> I’m also making slow progress on making childhurds usable on the ci.guix
> infrastructure (and probably elsewhere) for i586-gnu builds:
>
> https://issues.guix.gnu.org/58320
>
> ‘make assert-binaries-available’ reports 91.9% right now (commit
> 8b192c5550213911f930594f4fd7386f36618237).
I'm seeing 92.5% on staging, so if we're still planning on merging that
first IMO that branch is a bit more important.
> > • Address the blockers of <https://issues.guix.gnu.org/53214>, most of
> > which are issues in the installer.
>
> Mathieu fixed <https://issues.guix.gnu.org/57232> today.
>
> Discussions are ongoing regarding <https://issues.guix.gnu.org/55360>.
>
> How about meeting on #guix on IRC tomorrow Friday at 2PM CEST (UTC+2) to
> discuss the issues above and distribute work among ourselves? Who’s in?
>
> Ludo’.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-13 15:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07 9:49 ` Ludovic Courtès
2022-10-07 10:14 ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07 9:50 ` Ludovic Courtès
2022-10-07 9:53 ` Maxime Devos
2022-10-07 6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02 ` Ludovic Courtès
2022-10-10 7:57 ` Csepp
2022-10-12 20:40 ` Vagrant Cascadian
2022-10-13 15:06 ` Ludovic Courtès
2022-10-07 8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09 ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33 ` Efraim Flashner [this message]
2022-10-13 15:42 ` Christopher Baines
2022-10-20 13:49 ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07 ` Efraim Flashner
2022-10-21 8:51 ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42 ` Efraim Flashner
2022-10-22 20:22 ` Efraim Flashner
2022-10-26 9:01 ` Efraim Flashner
[not found] ` <87h6zyo811.fsf@gnu.org>
2022-10-21 8:43 ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21 9:30 ` Mathieu Othacehe
2022-10-31 17:40 ` Tobias Platen
2022-10-22 12:18 ` Release progress, week 2 Christopher Baines
2022-10-25 9:50 ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29 ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad 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=Y0gv0K4IexunvRx/@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=marius@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).