unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christina O'Donnell <cdo@mutix.org>
To: Christopher Baines <mail@cbaines.net>,
	Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>,
	70662@debbugs.gnu.org, 70663@debbugs.gnu.org
Subject: Re: Scheduling a new release?
Date: Tue, 14 May 2024 11:19:57 +0100	[thread overview]
Message-ID: <339167fe-c899-1303-166f-8040b49f0f59@mutix.org> (raw)
In-Reply-To: <87jzk4fofj.fsf@cbaines.net>

Hi,

On 08/05/2024 14:01, Christopher Baines wrote:
> I think it would be nice to have a new release, and indeed release more
> often, I think the way to get there is for less things to be broken
> between releases, such that releasing takes less effort in terms of
> testing and fixing things.
>
> To give some specific issues, I've run up against the recent issues with
> nss [1][2] and I don't think we could release with the nss package as is
> currently.
>
> 1: https://issues.guix.gnu.org/70662
> 2: https://issues.guix.gnu.org/70663

I can fix these by disabling tests, but I would prefer if someone with 
more experience packaging for guix could make a decision on it. 
Otherwise, I don't have any problem reducing the number of tests and 
disabling all tests on PowerPC at least.

I could also do some analysis if it was deemed necessary, inserting a 
patch to measure the timings of each test/cycle. Additionally, I could 
try packaging some of the versions between 0.88 and 0.98 to identify the 
exact change that could be to blame. However, both of these seem 
overkill, given the backlog of patches/issues we have left to get 
through, and the manpower we currently have to work with.

Would any of that be helpful?

> ...

Kind regards,

Christina



  parent reply	other threads:[~2024-05-14 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:12 Scheduling a new release? Simon Tournier
2024-05-06 11:17 ` Simon Tournier
2024-05-08 13:01 ` Christopher Baines
2024-05-14  9:41   ` Ludovic Courtès
2024-05-15 10:37     ` Andreas Enge
2024-05-14 10:19   ` Christina O'Donnell [this message]
2024-05-14 13:45     ` Christopher Baines
2024-05-21 23:42     ` bug#70662: Problems building nss@3.98.0 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=339167fe-c899-1303-166f-8040b49f0f59@mutix.org \
    --to=cdo@mutix.org \
    --cc=70662@debbugs.gnu.org \
    --cc=70663@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    --cc=zimon.toutoune@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).