unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: preparing the next release v0.15.0
Date: Mon, 2 Jul 2018 15:29:58 +0000	[thread overview]
Message-ID: <20180702152958.ycoll2ylfwjnyj7a@abyayala> (raw)
In-Reply-To: <87efgmj7jp.fsf@gnu.org>

Ludovic Courtès transcribed 2.1K bytes:
> Hello!
> 
> Clément Lassieur <clement@lassieur.org> skribis:
> 
> > I think we need https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30602 to
> > be fixed.
> 
> Done.   \o/
> 
> With Guile 2.2.4 now released, we can go ahead with 0.15.  Could people
> build the ISO installation image and give it a try:
> 
>   guix system disk-image --file-system-type=iso9660 gnu/system/install.scm
> 
> and then boot the resulting image (you can do that in QEMU if you
> prefer), and follow the instructions.
> 
> Likewise, tests of the binary Guix tarball would be welcome.  You can
> build it with:
> 
>   make guix-binary.x86_64-linux.tar.xz
> 
> For the record, some of the items Ricardo listed are not entirely
> addressed either (quoting Ricardo’s previous message):
> 
>   * Outstanding patches.  There are many patches in the queue at
>     guix-patches[1] that we should go through, comment on, and/or apply
>     before the release.  Who would like to join a task force to do that
>     together?  Let’s pick 5 patches each and review them so that we can
>     either comment to ask for changes or to apply them.
> 
>     [1]: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches
> 
>   * breakage since the last core-updates merge.  Since the long overdue
>     merge of the “core-updates” branch we have a few serious problems on
>     i686 (e.g. the gst-plugins-base package) and armhf.  Who would like to
>     lead an effort to investigate and fix these problems?  (Note: you
>     obviously don’t need to fix them yourself, just keep track of these
>     things and coordinate with others who investigate them.)

mysql is borked, as well as rust, if nothing changes in the last commits.
rust does not really matter since we do not have many depending packages
for it.
Mysql is more grave.

Any takers on mysql?

>   * collecting new features and big changes in NEWS.  The NEWS file
>     already lists some of the changes that the next release would provide
>     compared to 0.14.0, but we all know that there are more.  Who would
>     like to take charge of the NEWS file?  This involves asking people for
>     changes they would really like to be mentioned and coordinating with
>     other volunteers to search through all commits since v0.14.0 to find
>     noteworthy changes.
> 
> If we all focus on this, we could release by the end of the week or
> beginning of next week.  Let’s do that!  :-)

I could contribute some time on the NEWS file tomorrow.

> Ludo’.
> 

  parent reply	other threads:[~2018-07-02 15:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 21:07 preparing the next release v0.15.0 Ricardo Wurmus
2018-06-14  5:46 ` Pjotr Prins
2018-06-14  8:24   ` Ricardo Wurmus
2018-06-14 19:46     ` Pierre Neidhardt
2018-06-15  9:42     ` Ludovic Courtès
2018-06-14  9:14   ` Clément Lassieur
2018-07-02  9:44     ` Ludovic Courtès
2018-07-02 15:25       ` Efraim Flashner
2018-07-03 19:43         ` Ludovic Courtès
2018-07-03 20:24           ` Ricardo Wurmus
2018-07-04  7:28           ` Ludovic Courtès
2018-07-02 15:29       ` Nils Gillmann [this message]
2018-06-15  9:53 ` Ludovic Courtès
2018-06-15 13:11   ` Ricardo Wurmus
2018-06-18 20:31 ` Ricardo Wurmus
2018-06-18 22:44   ` Pierre Neidhardt
2018-06-19  1:49   ` Kei Kebreau
2018-06-19  7:25   ` Gábor Boskovits
2018-06-19 12:36   ` Marius Bakke
2018-06-19 12:48     ` Julien Lepiller
2018-06-19 14:32       ` swedebugia
2018-06-20 20:45       ` Ricardo Wurmus
2018-06-20 18:38     ` Kei Kebreau
2018-06-20 20:33       ` Nils Gillmann
2018-06-20 21:10         ` Ludovic Courtès
2018-06-21  1:05           ` Kei Kebreau
2018-06-21 10:45             ` Ricardo Wurmus
2018-06-20 21:11       ` Marius Bakke
2018-06-20 21:55       ` swedebugia
2018-06-21  1:06         ` Kei Kebreau

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=20180702152958.ycoll2ylfwjnyj7a@abyayala \
    --to=ng0@n0.is \
    --cc=clement@lassieur.org \
    --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 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).