From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: preparing the next release v0.15.0 Date: Mon, 02 Jul 2018 11:44:42 +0200 Message-ID: <87efgmj7jp.fsf@gnu.org> References: <87in6mbdkt.fsf@elephly.net> <20180614054636.pmoyt4sydtpmozmf@thebird.nl> <8736xpzq5i.fsf@lassieur.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fZvO5-00026l-Hp for guix-devel@gnu.org; Mon, 02 Jul 2018 05:44:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fZvO0-0003G4-LW for guix-devel@gnu.org; Mon, 02 Jul 2018 05:44:49 -0400 In-Reply-To: <8736xpzq5i.fsf@lassieur.org> (=?utf-8?Q?=22Cl=C3=A9ment?= Lassieur"'s message of "Thu, 14 Jun 2018 11:14:01 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Cc: guix-devel@gnu.org Hello! Cl=C3=A9ment Lassieur skribis: > I think we need https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D30602 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=3Diso9660 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=E2=80=99s 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=E2=80=99s 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=3Dguix-patches * breakage since the last core-updates merge. Since the long overdue merge of the =E2=80=9Ccore-updates=E2=80=9D branch we have a few seriou= s 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=E2=80=99t need to fix them yourself, just keep track of t= hese things and coordinate with others who investigate them.) * 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=E2=80=99s do that! :-) Ludo=E2=80=99.