unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: guix-devel@gnu.org
Subject: Re: Plan for a release!
Date: Tue, 25 Feb 2020 10:47:39 -0500	[thread overview]
Message-ID: <86lfoqy8h0.fsf@dismail.de> (raw)
In-Reply-To: <87pne3d5t6.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 24 Feb 2020 22:38:29 +0100")

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Guix!
>
> I’m going on vacation for a bit, but I think we should finally get that
> release out!  Here’s the list of things to do I have in mind:
>
>   • We need Guile 3.0.1 to fix ‘guix pull’ etc. on AArch64 and possibly
>     JIT on ARMv7:
>
>       https://issues.guix.gnu.org/issue/39266
>       https://issues.guix.gnu.org/issue/39208
>
>   • More testing of the guided installer and related issues:
>
>      https://issues.guix.gnu.org/issue/39729
>      https://issues.guix.gnu.org/issue/39712

I'll volunteer to do this on Thursday.  I've got two Macbooks 7,1 and a
2008 Macbook Pro that I can test on.  

>
>   • Fix the weird default font in GNOME Terminal, as sirgazil reported
>     on help-guix.
>
>   • Ensure that the desktop environments provided by the installer
>     actually work (GNOME, Xfce, MATE, etc.).  It’d be great to have
>     automated tests for these!

I do that as well this Thursday.

>
>   • (Optionally) have an automated test that installs the binary tarball
>     on Debian or similar.
>
>   • Address as many of the bugs marked “important” or “serious” as
>     possible.  Should we organize a bug-squashing week?  :-)
>
>   • We already have “make assert-binaries-available”, but at the Guix
>     Days we came up with the idea of having ‘guix weather
>     --release-critical’ or similar, which would ensure that all the
>     relevant jobs pass (packages, cross-builds, system tests, etc.).
>     I’ll see if I can do something in that area.
>
> What’s missing from the list?
>
> I don’t think we’ll wait for the ‘core-updates’ merge, but who knows.
>
> As you see there’s a lot of testing in there, plus the need to keep
> things on track!  If someone wants to be the “master of time” and make
> sure we don’t enter and endless add-feature/break/fix loop, that’d be
> welcome!
>
> Thoughts?
>
> Ludo’.
>

-- 
Joshua Branson
Sent from Emacs and Gnus

  parent reply	other threads:[~2020-02-25 15:47 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 21:38 Plan for a release! Ludovic Courtès
2020-02-24 22:55 ` Vincent Legoll
2020-02-25 14:00   ` Jonathan Brielmaier
2020-02-25 15:15     ` Vincent Legoll
2020-02-24 23:35 ` zimoun
2020-02-25 15:47 ` Joshua Branson [this message]
2020-03-05  4:54 ` jbranso
2020-03-08 12:04   ` pelzflorian (Florian Pelz)
2020-03-08 21:03     ` kmscon not working on MacBook Ludovic Courtès
2020-03-09  7:43       ` pelzflorian (Florian Pelz)
2020-03-09  9:48         ` Vincent Legoll
2020-03-09 16:45         ` Ludovic Courtès
2020-03-11  7:14           ` pelzflorian (Florian Pelz)
2020-03-11  7:25             ` pelzflorian (Florian Pelz)
2020-03-20  8:48             ` pelzflorian (Florian Pelz)
2020-03-20  8:51               ` pelzflorian (Florian Pelz)
2020-03-25 23:00               ` pelzflorian (Florian Pelz)
2020-03-26  2:26                 ` Bengt Richter
2020-03-26 16:53                   ` pelzflorian (Florian Pelz)
2020-03-29 10:26                     ` pelzflorian (Florian Pelz)
2020-03-08 12:35   ` Gnome takes more than 5 minutes to start Ricardo Wurmus
2020-03-08 21:04   ` Btrfs/udev issue Ludovic Courtès
2020-03-05 13:42 ` Plan for a release! jbranso
2020-03-05 16:45   ` sirgazil
2020-03-06 16:32     ` Joshua Branson
2020-03-05 21:09   ` Jan
2020-03-06 16:33     ` Joshua Branson
2020-03-06 16:51     ` Thunar cannot launch gio-launch-desktop Ricardo Wurmus
2020-03-06 17:57       ` Jan
2020-03-06 21:51         ` Ricardo Wurmus
2020-03-06 23:59           ` Jan
2020-03-07 23:41           ` Jan
2020-03-08  9:08             ` Ricardo Wurmus
2020-03-08 22:05               ` Jan
2020-03-08 23:41               ` Jan
2020-03-09 22:41               ` Jan
2020-03-06  6:44   ` Plan for a release! pelzflorian (Florian Pelz)
2020-03-06  9:58     ` John Soo
2020-03-08 12:33   ` Ricardo Wurmus
2020-03-08 21:10   ` Ludovic Courtès
2020-03-12 13:54 ` Ludovic Courtès
2020-03-18 16:53   ` Ludovic Courtès
2020-03-18 17:31     ` Ricardo Wurmus
2020-03-18 17:49     ` Mathieu Othacehe
2020-03-20 10:52       ` Mathieu Othacehe
2020-03-20 13:13         ` Gábor Boskovits
2020-03-20 13:58           ` Mathieu Othacehe
2020-03-21 15:46         ` Ludovic Courtès
2020-03-23 14:05           ` Mathieu Othacehe
2020-03-26 11:55             ` Ludovic Courtès
2020-03-26 12:37               ` Vincent Legoll
2020-03-26 14:24                 ` 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=86lfoqy8h0.fsf@dismail.de \
    --to=jbranso@dismail.de \
    --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).