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: Releasing 0.9.1
Date: Fri, 05 Feb 2016 14:46:24 +0100	[thread overview]
Message-ID: <87d1sbi827.fsf@gnu.org> (raw)

Hello!

I suggest that we release 0.9.1 as soon as we get less than 2 kernel
panic reports per day!

(Just kidding.)

Seriously, I think we should be aiming for a release by the end of the
month.  Here a few rather low-hanging fruits that I think we should
address:

  • Have a GNOME meta-package, or a ‘%gnome-packages’ variable, or
    something like that.  We should provide an example of how to get a
    GNOME setup.  I think several of you have that already.  宋文武?

  • Proper ‘package-with-python2’ (see <http://bugs.gnu.org/22437>.)
    It just needs more testing and adjusting existing packages (fewer
    lines of code, yay!).

  • There are several bugs reports open regarding container-related test
    failures.  I think we should make sure they are addressed and close
    them.  David?

  • The nscd issue in the installer image: <http://bugs.gnu.org/22209>.
    I’ll try to reproduce it in a VM and debug from there.

  • Incorporate root-encryption fixes (<http://bugs.gnu.org/21843>) and
    documentation by Petter.  Petter and Albin, among others, are
    already using an encrypted-root setup AIUI, so it’s “just a matter”
    of consolidating it.  See also
    <http://lists.gnu.org/archive/html/help-guix/2016-01/msg00118.html>.

  • The ‘guile@1.8’ syntax patch.  Mathieu?

  • Possibly the GitHub updater, which seemed pretty much ready.  Ben?

Anything else?

I think we should all focus on these tasks and other bugs at
<http://bugs.gnu.org/guix> (help on bug triage is welcome!).

It may be that I won’t be able to handle this release myself because
I’ll soon be busy for family reasons.  :-)  I think it’s a great
opportunity to try and delegate to someone else (I have a few potential
victims in mind that I need to contact ;-)).  The whole process is
documented in ‘doc/release.org’ in guix-maintenance.git and hopefully
intelligible.

Ludo’.

             reply	other threads:[~2016-02-05 13:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 13:46 Ludovic Courtès [this message]
2016-02-05 13:51 ` Releasing 0.9.1 Andreas Enge
2016-02-07 12:13 ` Ben Woodcroft
2016-02-07 12:48   ` Ricardo Wurmus
2016-02-07 20:44     ` Ludovic Courtès
2016-02-07 20:54       ` Ben Woodcroft
2016-02-08 21:21 ` Mathieu Lirzin
2016-02-25 17:51 ` Ludovic Courtès
2016-02-25 18:04   ` Ricardo Wurmus
2016-02-25 19:27   ` Leo Famulari
2016-02-26 23:15     ` Ludovic Courtès
2016-02-25 20:11   ` Andreas Enge
2016-02-26 23:16     ` Ludovic Courtès
2016-03-09 13:14   ` Ludovic Courtès
2016-03-09 14:41     ` Ludovic Courtès
2016-03-10 16:23       ` 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=87d1sbi827.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.