From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: preparing the next release v0.15.0 Date: Mon, 18 Jun 2018 22:31:24 +0200 Message-ID: <87tvpzvntv.fsf@elephly.net> References: <87in6mbdkt.fsf@elephly.net> 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]:46659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fV2SM-0001MS-Dt for guix-devel@gnu.org; Mon, 18 Jun 2018 18:17:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fV2SJ-0006GY-46 for guix-devel@gnu.org; Mon, 18 Jun 2018 18:17:02 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21149) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fV2SI-0006GM-Qj for guix-devel@gnu.org; Mon, 18 Jun 2018 18:16:59 -0400 In-reply-to: <87in6mbdkt.fsf@elephly.net> 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: guix-devel@gnu.org Hi Guix, I wrote almost 6 days ago: > Here are a bunch of things that we should look into: > > * 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. > [=E2=80=A6] > Did I miss anything? Who wants to help? We aim for a release on June 30, 2018. Unfortunately, so far nobody has come forward to help us coordinate one of these three tasks. Any volunteers? -- Ricardo