all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Plan for 0.9.0
Date: Mon, 02 Nov 2015 10:45:18 +0100	[thread overview]
Message-ID: <87pozslopd.fsf@gnu.org> (raw)
In-Reply-To: <87io6b943m.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 12 Oct 2015 23:19:57 +0200")

Status update:

ludo@gnu.org (Ludovic Courtès) skribis:

> In addition to the nice stuff we already have, it’d be nice to add:
>
>   • wip-container, I think we’re almoooost there;

Done (a couple of small testing issues need to be solved.)

>   • finalize multiple-server support in ‘guix substitute’;

Done.

>   • maybe merge wip-loogson2f or help generalize the issues identified
>     in that branch? doable?

Half-done.  Will finish for the next release.

>   • low-hanging fruits in the Freedesktop side (adding a udisk service,
>     fixing D-Bus service activation, for instance; what else?)

Done.

>   • add the ‘guix install’ alias discussed a while back;

Postponed.

>   • /etc/environment and pam_env, as was suggested;

Probably postponed.

>   • bug fixes, lots.

I’ll go through the list again.

I would like to work on the release this Wednesday, Nov. 4th, with the
announcement going out sometime between Wednesday and Friday.

I’ll post a GuixSD installation image for testing hopefully later today.

In the meantime, please see what you can do to fix these:

  http://hydra.gnu.org/eval/107728#tabs-still-fail
  http://bugs.gnu.org/guix

TIA!  :-)

Ludo’.

      parent reply	other threads:[~2015-11-02  9:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 21:19 Plan for 0.9.0 Ludovic Courtès
2015-10-13 13:15 ` Daniel Pimentel
2015-10-13 14:37   ` Ludovic Courtès
2015-10-13 15:01   ` Alex Vong
2015-10-13 15:27     ` Ricardo Wurmus
2015-10-13 18:26       ` Mathieu Lirzin
2015-10-13 18:30         ` Taylan Ulrich Bayırlı/Kammer
2015-10-14 19:58     ` Ludovic Courtès
2015-10-14 20:06       ` Mathieu Lirzin
2015-10-14 21:44         ` Ludovic Courtès
2015-10-14 22:02           ` Eric Bavier
2015-10-15 12:28             ` Mathieu Lirzin
2015-10-15 12:33               ` Thompson, David
2015-10-15 12:51                 ` Mathieu Lirzin
2015-10-15 13:10                   ` Thompson, David
2015-10-15 13:15                     ` Daniel Pimentel
2015-10-15 14:11                       ` Christopher Allan Webber
2015-10-15 14:43                         ` Ludovic Courtès
2015-10-15 13:40                     ` Mathieu Lirzin
2015-10-15 15:31                 ` Taylan Ulrich Bayırlı/Kammer
2015-10-15 19:27                   ` Ludovic Courtès
2015-10-16  4:14                 ` Alex Vong
2015-10-16  7:44                   ` Mathieu Lirzin
2015-10-16 11:09                     ` Alex Vong
2015-10-16  8:10                   ` Registering GC roots Ludovic Courtès
2015-10-16 12:56                     ` Alex Vong
2015-10-16 15:41                       ` Ludovic Courtès
2015-10-16 15:55                         ` Alex Vong
2015-10-16 17:21                           ` Andreas Enge
2015-10-16 16:28                         ` Mathieu Lirzin
2015-10-15 14:41               ` Plan for 0.9.0 Ludovic Courtès
2015-10-15 15:07                 ` Mathieu Lirzin
2015-11-02  9:45 ` Ludovic Courtès [this message]

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=87pozslopd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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.