From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, guix-maintainers@gnu.org
Subject: Re: New 'version-1.3.0' branch and lifting string freeze on master
Date: Sun, 18 Apr 2021 12:09:45 +0200 [thread overview]
Message-ID: <87k0oznbti.fsf@gnu.org> (raw)
In-Reply-To: <87mttwkaxn.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 17 Apr 2021 14:44:52 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> With the remaining issues to be tackled for the current release (v1.3.0)
> due tomorrow, I think we may need a bit of extra time to fix them and do
> more testing. These are the remaining issues (obtained by pressing the
> 'b' key in Emacs Debbugs while visiting the parent issue with
> 'debbugs-gnu-bugs RET 47297 RET'). The release task issue can also be
> viewed at https://issues.guix.gnu.org/47297.
>
> 47808 important Bone Baboon guile-git-0.5.0.drv build failed on i686-linux
> 47567 important Alexandru-Sergiu M Installer crash in 'uuid->string' for a FAT16 partition
> 44872 important Tim Magee GuixSD 1.2.0 installer fails with exception when formatting drive
> 33848 important Ludovic Courtès Store references in SBCL-compiled code are "invisible"
> 47841 normal Julien Lepiller [release 1.2.1] could not install on foreign distro
> 47745 normal Mathieu Othacehe ldap test is failing
> 47744 normal Mathieu Othacehe nfs-root-fs test is failing
I agree that we need a bit more time to address these, hopefully get
‘wip-ungrafting’ merged, and above all get more testing.
There are other items from doc/release.org in maintenance.git that will
have to be addressed, such as the dreaded NEWS update and companion blog
post.
> To avoid keep master in string freeze longer, I've now created the
> 'release-v1.3.0' branch where the fixes for the remaining blocking
> issues should go.
Nitpick: could we rename it to ‘version-1.3.0’, similar to the previous
release branches?
BTW, are we going for 1.3.0 rather than 1.2.1? I’m fine either way,
it’s true that 1.3.0 might better reflect the amount of work that has
gone into it…
> I'll now attempt to produce a first release candidate (RC) via the
> release tooling.
Yay! If we eventually merge ‘wip-ungrafting’, we should have at least
one RC built with that branch merged.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-04-18 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 18:44 New 'version-1.3.0' branch and lifting string freeze on master Maxim Cournoyer
2021-04-17 18:47 ` Leo Famulari
2021-04-18 10:09 ` Ludovic Courtès [this message]
2021-04-18 12:08 ` 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
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=87k0oznbti.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=maxim.cournoyer@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 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).