From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: preparing the next release v0.15.0 Date: Tue, 19 Jun 2018 09:25:17 +0200 Message-ID: References: <87in6mbdkt.fsf@elephly.net> <87tvpzvntv.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002df4f6056ef9963f" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVB19-00080u-1Z for guix-devel@gnu.org; Tue, 19 Jun 2018 03:25:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVB17-0003We-Us for guix-devel@gnu.org; Tue, 19 Jun 2018 03:25:31 -0400 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]:43785) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVB17-0003WU-Nv for guix-devel@gnu.org; Tue, 19 Jun 2018 03:25:29 -0400 Received: by mail-io0-x235.google.com with SMTP id t6-v6so19146613iob.10 for ; Tue, 19 Jun 2018 00:25:29 -0700 (PDT) In-Reply-To: <87tvpzvntv.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: Ricardo Wurmus Cc: Guix-devel --0000000000002df4f6056ef9963f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ricardo Wurmus ezt =C3=ADrta (id=C5=91pont: 2018. j=C3= =BAn. 19., K, 0:17): > 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. > This week I'm on vacation. I can start helping with the patches the next week. Are there any to priority ones? > > > > [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 seri= ous problems on > > i686 (e.g. the gst-plugins-base package) and armhf. Who would like t= o > > 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= these > > 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 fo= r > > 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 > > > --0000000000002df4f6056ef9963f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ricardo Wurmus= <rekado@elephly.net> ezt = =C3=ADrta (id=C5=91pont: 2018. j=C3=BAn. 19., K, 0:17):
Hi Guix,

I wrote almost 6 days ago:

> Here are a bunch of things that we should look into:
>
> * Outstanding patches.=C2=A0 There are many patches in the queue at >=C2=A0 =C2=A0guix-patches[1] that we should go through, comment on, and= /or apply
>=C2=A0 =C2=A0before the release.=C2=A0 Who would like to join a task fo= rce to do that
>=C2=A0 =C2=A0together?=C2=A0 Let=E2=80=99s pick 5 patches each and revi= ew them so that we can
>=C2=A0 =C2=A0either comment to ask for changes or to apply them.

This week I'm on vacation. I can start= helping with the patches the next week.
Are there any to priorit= y ones?

=C2=A0
>
>=C2=A0 =C2=A0[1]: https://debbug= s.gnu.org/cgi/pkgreport.cgi?package=3Dguix-patches
>
> * breakage since the last core-updates merge.=C2=A0 Since the long ove= rdue
>=C2=A0 =C2=A0merge of the =E2=80=9Ccore-updates=E2=80=9D branch we have= a few serious problems on
>=C2=A0 =C2=A0i686 (e.g. the gst-plugins-base package) and armhf.=C2=A0 = Who would like to
>=C2=A0 =C2=A0lead an effort to investigate and fix these problems?=C2= =A0 (Note: you
>=C2=A0 =C2=A0obviously don=E2=80=99t need to fix them yourself, just ke= ep track of these
>=C2=A0 =C2=A0things and coordinate with others who investigate them.) >
> * collecting new features and big changes in NEWS.=C2=A0 The NEWS file=
>=C2=A0 =C2=A0already lists some of the changes that the next release wo= uld provide
>=C2=A0 =C2=A0compared to 0.14.0, but we all know that there are more.= =C2=A0 Who would
>=C2=A0 =C2=A0like to take charge of the NEWS file?=C2=A0 This involves = asking people for
>=C2=A0 =C2=A0changes they would really like to be mentioned and coordin= ating with
>=C2=A0 =C2=A0other volunteers to search through all commits since v0.14= .0 to find
>=C2=A0 =C2=A0noteworthy changes.
>
[=E2=80=A6]
> Did I miss anything?=C2=A0 Who wants to help?

We aim for a release on June 30, 2018.=C2=A0 Unfortunately, so far nobody h= as
come forward to help us coordinate one of these three tasks.

Any volunteers?

--
Ricardo


--0000000000002df4f6056ef9963f--