From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: =?utf-8?Q?Let=E2=80=99s?= freeze and build =?utf-8?Q?=E2=80=98core-updates=E2=80=99!?= Date: Tue, 14 Feb 2017 16:00:15 +0100 Message-ID: <87zihoizr4.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> References: <87mvdpw3b3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdead-0007vA-9h for guix-devel@gnu.org; Tue, 14 Feb 2017 10:00:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cdeaY-0000ML-Dd for guix-devel@gnu.org; Tue, 14 Feb 2017 10:00:23 -0500 In-Reply-To: <87mvdpw3b3.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= , guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Hello Guix! > > Since I=E2=80=99m about to leave keyboard for a couple of weeks, here=E2= =80=99s a to-do > list for those of you who=E2=80=99ll be around. :-) > > The last things I wanted to push for =E2=80=98core-updates=E2=80=99 were = a reproducible > Guile (done in b5efd14a9add1bcb4a44fa5b9c1b47706f3df9da), and a subset > or all of the aarch64 patches, depending on their status (should not be > a blocker IMO). > > So, here=E2=80=99s a plan: > > =E2=80=A2 Once Efraim has pushed some of the aarch64 patches, do another > evaluation of the =E2=80=9Ccore=E2=80=9D package set for that branch,= and check for > anything wrong. From there on, forbid full-rebuild changes. > > =E2=80=A2 Once the =E2=80=9Ccore=E2=80=9D subset builds correctly on al= l the supported > platforms (those that Hydra supports), merge =E2=80=98master=E2=80=99= . Maybe update > a couple of things like GnuTLS while we=E2=80=99re at it. From there= on > forbid non-trivial changes. > > =E2=80=A2 Build all the packages. (To do that, someone with access to = Hydra > must change the =E2=80=9Csubset=E2=80=9D argument to =E2=80=9Call=E2= =80=9D in the config of the > =E2=80=98core-updates=E2=80=99 jobset.) > > =E2=80=A2 Fix things. > > =E2=80=A2 Once most regressions have been addressed and most binaries a= re > available, merge =E2=80=98core-updates=E2=80=99 into =E2=80=98master= =E2=80=99. > > How does that sound? This sounds great. I have a question: The 'staging' branch contains a number of minor updates and it's been more than a month since the last merge. Should we do a staging evaluation first (i.e. next few days), or just merge it to core-updates? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlijG38ACgkQoqBt8qM6 VPrpNQf+OeSjkE8179/t0nKxovQS1qKPAToRMCGQIYmMmWb/je/ar3ugdcFo8a6p +Bvc3wPHTt4tlcfB0eQx/5Aek+JBKc0VVDeYD/UCYEJuzrduR0fopjzcfz1qIolI T7OLiHhqzjXGPL9T70jx19UDDEWKfKNHEhRou6d1t6IDFxkuX4eMM8VAwPdwT9Kp 4h4WdCq1YjL1s9dRaCYOHOnUJW4s5N6Sv/bigtLaJ7YzqbsEoqEJzK1Opq2O16MQ NszLTWeyBFpDTAXIzTVjZ7+c1BdLCfSJireEhTLTRDSQ5PU6qk7risE/u72tI/ze kDmdURSlzCgllvic9iTHL+TFCPPjgg== =14zs -----END PGP SIGNATURE----- --=-=-=--