From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Planning for the next release
Date: Mon, 03 Apr 2017 10:26:54 +0200
Message-ID: <87pogtsxpt.fsf@gnu.org>
References: <87wpb7ym78.fsf@gnu.org> <20170403002828.GA2288@jasmine>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48742)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cuxKG-00052X-HZ
	for guix-devel@gnu.org; Mon, 03 Apr 2017 04:27:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cuxKD-0000xi-Br
	for guix-devel@gnu.org; Mon, 03 Apr 2017 04:27:00 -0400
In-Reply-To: <20170403002828.GA2288@jasmine> (Leo Famulari's message of "Sun,
	2 Apr 2017 20:28:28 -0400")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>

Hi!

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Mar 30, 2017 at 02:37:47PM +0200, Ludovic Court=C3=A8s wrote:
>> Hello Guix!
>>=20
>> It=E2=80=99s time to plan for the next release!  Here=E2=80=99s what we =
maintainers
>> think should be done for the next release, which would hopefully happen
>> within less than a month:
>>=20
>> Please share your thoughts!
>
> I just pushed a tzdata update to a new staging branch. Let's build and
> merge this branch before the next release.

We can do that, but should it be a blocker?  Anyway, let=E2=80=99s try and =
we=E2=80=99ll
see.

BTW:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix refresh -l -e '(@@ (gnu packages base) tzdata)'
Building the following 239 packages would ensure 442 dependent packages are=
 rebuilt
--8<---------------cut here---------------end--------------->8---

I was expecting to see fewer packages depending on this one since
3ffaec136fab017e6cc094287da207cf30f05974.  Perhaps in the =E2=80=98staging=
=E2=80=99
branch we should migrate a few more packages to =E2=80=98tzdata-2017a=E2=80=
=99?

Thanks,
Ludo=E2=80=99.