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: Fri, 15 Jun 2018 11:53:19 +0200 Message-ID: <871sd8v0j4.fsf@gnu.org> 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]:51330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fTlQ2-0008SF-8Q for guix-devel@gnu.org; Fri, 15 Jun 2018 05:53:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fTlQ1-0001lf-B3 for guix-devel@gnu.org; Fri, 15 Jun 2018 05:53:22 -0400 In-Reply-To: <87in6mbdkt.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 13 Jun 2018 23:07:14 +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: Ricardo Wurmus Cc: guix-devel@gnu.org Hello! The plan looks good to me! Ricardo Wurmus skribis: > * 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. Agreed with all this. :-) > * Finding a date. Some of the fixes that need to be included may have > to end up on core-updates. According to my calendar core-updates will > be frozen on <2018-08-06 Mon> and be merged on <2018-08-20 Mon> at the > latest. That=E2=80=99s a little late, so if we can solve problems on t= he > master branch with architecture-specific workarounds that don=E2=80=99t= result > in rebuilding the world (in addition to proper fixes on core-updates) > that would be best. What do you think: is July 27 (2018) realistic? I would prefer an earlier date even, perhaps around June 30. WDYT? Thanks, Ludo=E2=80=99.