unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: What for 0.5?
Date: Mon, 09 Dec 2013 22:19:26 +0100	[thread overview]
Message-ID: <87siu190yp.fsf@gnu.org> (raw)
In-Reply-To: <87a9ghy5hb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 03 Dec 2013 22:44:32 +0100")

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

> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> I think we should aim for a 0.5 release within 2 to 4 weeks.  So, what
>> do we put in there?
>>
>> We already have nice things:
>>
>>   • Better patch handling.
>>
>>   • MIPS/N32 port.
>>
>>   • Monads, and other API improvements.
>>
>> In addition, I think we should:
>>
>>   • Switch to GCC 4.8 as the default compiler, and thus rebuild the
>>     bootstrap binaries; optionally, arrange so that those bootstrap
>>     binaries are the fixed point.
>>
>>   • Merge the ‘loongson’ branch in ‘core-updates’.
>>
>>   • Come up with a new VM demo image, with a better (gnu system) API,
>>     and using a new dmd release (more on that later).
>>
>>   • More packages, ideally in the GUI/desktop area (you can help! :-)).
>>
>> What do you think?  Anything else?
>
> I think we now have most of what we wanted, so it’s now reasonable to
> aim for a release within 1 week.  I’ll spend most of that time on the VM
> image, and looking at open bugs.  Help welcome!

So weeks take a bit more than 7 days it seems, but we’re getting there!
I’ve worked on the (gnu system) module, now used to build the VM image,
so I think the important pieces are in place (I’ll write about it.)

I’d like to release this Wednesday, so please do not push anything that
triggers big rebuilds until then.

However, it’s still time to look at <http://bugs.gnu.org/guix>.  :-)

Ludo’.

      reply	other threads:[~2013-12-09 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 22:01 What for 0.5? Ludovic Courtès
2013-11-05 18:10 ` Cyril Roelandt
2013-11-06 13:04   ` Ludovic Courtès
2013-11-11 17:50     ` Andreas Enge
2013-11-11 20:35       ` Ludovic Courtès
2013-12-03 21:44 ` Ludovic Courtès
2013-12-09 21:19   ` 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

  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=87siu190yp.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 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).