all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: 0.8.3 for mid-July?
Date: Wed, 1 Jul 2015 09:53:20 -0400	[thread overview]
Message-ID: <CAJ=RwfYPcpujqh0Jpi3zaMmq20PLpPXH0Y8Pdt78v0B85k3mSQ@mail.gmail.com> (raw)
In-Reply-To: <87y4j0rosq.fsf@gnu.org>

On Wed, Jul 1, 2015 at 9:27 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hello!
>
> I think we should release 0.8.3 for mid to end July.

That sounds good.  I guess now is a good time to mention that I will
be AFK from July 10th to the 17th.

> The relevant things to be done include:
>
>   • Merging wip-diet and wip-environment, and maybe wip-container,
>     though that one could just as well be merged afterwards.

I looked at wip-environment last night and I liked what I saw.  I did
a couple of smoke tests and everything worked as expected.  Thanks for
figuring out some of the difficult issues there, like only including
the relevant outputs in the environment.

I'd really like wip-container to make it in so that we can start
showing it off, but I'm currently blocked on a working
eval-in-container implementation.  Perhaps I could save that for next
release and polish what works ('guix environment --container', 'guix
system container')?

>   • We must sit down and fix as many bugs as possible.
>     <http://bugs.gnu.org/20765> is a blocker IMO, but help is needed
>     from Pythonistas.  <http://bugs.gnu.org/20888> must be fixed too,
>     but there are many others.
>
>   • Several people reported getting a kernel panic, instead of a Guile
>     prompt, when something goes wrong during early boot (in the initrd.)
>     I haven’t been able to reproduce it in a VM; if someone could
>     reproduce it, that would be great.
>
> There are optimizations that I would like to look into it, though they
> are not blocker IMO:
>
>   • ‘guix build hydra -n’ literally takes ages, as Eric noted, so that
>     needs to be investigated.
>
>   • ‘guix system’ is quite slow, but it’s apparently computing the same
>     derivations several times, which must be fixed.
>
> Anything else?  Comments?

Let's do this! :)

- Dave

  reply	other threads:[~2015-07-01 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 13:27 0.8.3 for mid-July? Ludovic Courtès
2015-07-01 13:53 ` Thompson, David [this message]
2015-07-01 15:04   ` Ludovic Courtès
2015-07-04 14:45 ` Ludovic Courtès
2015-07-06  7:28   ` Federico Beffa
2015-07-11 23:34 ` Ludovic Courtès
2015-07-17 16:48 ` 0.8.3 update 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfYPcpujqh0Jpi3zaMmq20PLpPXH0Y8Pdt78v0B85k3mSQ@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.