From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Planning for the next release Date: Fri, 31 Mar 2017 13:57:32 +0000 Message-ID: <20170331135732.pkobwwkzuojil4v3@abyayala> References: <87wpb7ym78.fsf@gnu.org> 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]:53976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ctx3s-0001Sx-J5 for guix-devel@gnu.org; Fri, 31 Mar 2017 09:57:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ctx3o-0003m6-Fu for guix-devel@gnu.org; Fri, 31 Mar 2017 09:57:56 -0400 Content-Disposition: inline In-Reply-To: <87wpb7ym78.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?= Cc: guix-devel , John Darrington Ludovic Court=C3=A8s transcribed 3.0K bytes: > 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 > 1. =E2=80=98core-updates=E2=80=99 merged. We=E2=80=99re almost ther= e! >=20 > 2. =E2=80=98wip-installer=E2=80=99 retested, and probably merged. >=20 > I think the prerequisite for it would be to do some more testing. > Last time people reported glitches here and there but John has > done quite a bit of work since then. John: what about doing > another round of tests? >=20 > In the installation image, we should probably make the installer > optional and mark it as =E2=80=9Cbeta=E2=80=9D or something like = that. That will > leave us time to iron out remaining issues, and will avoid having > people expect a rock-solid Debian-style installer. >=20 > As far as review is concerned, we can probably do a quick and > lightweight review process since that=E2=80=99s quite a big chunk= of code > and we don=E2=80=99t want the branch to block indefinitely. So w= e can do > that quick process, and then incrementally improve it if needed. > I think it=E2=80=99s a reasonable approach given that the install= er is > mostly an independent component. >=20 > John, everyone: thoughts? >=20 > 3. UEFI support documented and possibly improved. >=20 > We can certainly document the UEFI setup and add the /boot/efi > partition in some of the =E2=80=98operating-system=E2=80=99 examp= les. >=20 > The more difficult part is the installation: do we need to make a > second, UEFI-specific, installation image? When I installed > GuixSD on UEFI, I booted our installation image as =E2=80=9Clegac= y=E2=80=9D, but > then GRUB would default to a legacy install, not a UEFI install: >=20 > https://lists.gnu.org/archive/html/guix-devel/2016-12/msg00799.= html >=20 > I=E2=80=99m not sure exactly what needs to be done. Thoughts? >=20 > 4. Fix low-hanging fruits at ; your help > welcome! >=20 > Please share your thoughts! >=20 > Ludo=E2=80=99. Questions about UEFI are getting more frequent, so I'd say this is good to document it properly. On my side, people will and have asked for the intermediate time how/if the http_proxy of Guix works. If someone has been using it with an SOCKS5 proxy successfully, I'd would like to have this added to documentation as well. My own experiment ended up with a shot in the foot where I had to roll back because Guix was now unable to do anything at all. Maybe as a 'food for thought': More filesystems.. I have an work in progress patch for XFS, but it's not completely clear how filesystems are supposed to be built. All static? All dynamic? Both?