Re: Release v1.2 timetable

2020-10-26 Thread Ludovic Courtès
zimoun skribis: > On Wed, 21 Oct 2020 at 11:14, Ludovic Courtès wrote: > >> > >> >> For that we need a Guile-Git release, which could be made anytime now. >> Mathieu, do you want to take care of it? If not, I can do it. > > Now, the initial list is done,

Re: Release v1.2 timetable

2020-10-23 Thread zimoun
Hi, On Wed, 21 Oct 2020 at 11:14, Ludovic Courtès wrote: > > > > For that we need a Guile-Git release, which could be made anytime now. > Mathieu, do you want to take care of it? If not, I can do it. Now, the initial list is done, right? Commit

Re: Release v1.2 timetable

2020-10-22 Thread Mathieu Othacehe
Hey Ludo, > For that we need a Guile-Git release, which could be made anytime now. > Mathieu, do you want to take care of it? If not, I can do it. Done with fbac2572f6ab6bf709302b0a270e1e66a942ba07. Thanks, Mathieu

Re: Release v1.2 timetable

2020-10-21 Thread Ludovic Courtès
Hello! zimoun skribis: > For that we need a Guile-Git release, which could be made anytime now. Mathieu, do you want to take care of it? If not, I can do it. > Done! :-) Thanks, Ludo’.

Re: Release v1.2 timetable

2020-10-09 Thread Danny Milosavljevic
On Fri, 9 Oct 2020 20:25:57 +0200 Andreas Enge wrote: > On Tue, Oct 06, 2020 at 09:57:20AM +0200, Mathieu Othacehe wrote: > > The CI is already building substitutes for two images > > (hurd-barebones-qcow2-image and pine64-barebones-raw-image). We could > > maybe release 1.2 version of those

Re: Release v1.2 timetable

2020-10-09 Thread Andreas Enge
On Tue, Oct 06, 2020 at 09:57:20AM +0200, Mathieu Othacehe wrote: > The CI is already building substitutes for two images > (hurd-barebones-qcow2-image and pine64-barebones-raw-image). We could > maybe release 1.2 version of those images. Nice! For completely selfish reasons, I would like to also

Re: Release v1.2 timetable

2020-10-07 Thread Danny Milosavljevic
Hi, On Wed, 7 Oct 2020 16:51:46 +0200 zimoun wrote: > BTW, is this Bug #43720 [5] blocking for the release too? I'd say yes. If homedirs are not created, one can't use the shiny new Guix system, now can one? pgpD0bhyarlf9.pgp Description: OpenPGP digital signature

Re: Release v1.2 timetable

2020-10-07 Thread Danny Milosavljevic
Hi zimoun, On Wed, 7 Oct 2020 17:39:44 +0200 Danny Milosavljevic wrote: > > BTW, is this Bug #43720 [5] blocking for the release too? > > > > Well, what is the status and the plan about this armhf topic? The short term plan is to only build 32 bit releases on 32 bit machines and 64 bit

Re: Release v1.2 timetable

2020-10-07 Thread Danny Milosavljevic
Hi, On Wed, 7 Oct 2020 16:51:46 +0200 zimoun wrote: > I have read Bug #43513 and Patch #43591 [1,2] and the table [3] is not > really encouraging. :-( This bug has serious repercussions for bootstrapping--and thus for the entire GNU Guix distribution (not to mention those other distributions

Re: Release v1.2 timetable

2020-10-07 Thread zimoun
Dear Danny, On Tue, 29 Sep 2020 at 17:08, Danny Milosavljevic wrote: > > b. fix bugs severity:important,serious [3,4] or report > > Bug #43513 means that all armhf substitutes built for armhf on anything else > than armhf (especially those built on aarch64) are untrustworthy. > > I'm working

Re: Release v1.2 timetable

2020-10-07 Thread zimoun
> > I'm actually not really sure how one would use the installer on one of > > the boards. I think the bare-bones disk-images would be best; just > > download it and flash it onto the board or an SD card and edit > > /etc/config.scm to add your user and services. Or to boot up into the > >

Re: Release v1.2 timetable

2020-10-07 Thread zimoun
Hi Matthieu, On Tue, 6 Oct 2020 at 08:57, Mathieu Othacehe wrote: > > What is the status of the installer? > > I don't think there are known issues at the moment. I have started > testing it on my laptop, by booting on a flash drive and installing on > another one, while being quite anxious for

Re: Release v1.2 timetable

2020-10-06 Thread Mathieu Othacehe
> I'm actually not really sure how one would use the installer on one of > the boards. I think the bare-bones disk-images would be best; just > download it and flash it onto the board or an SD card and edit > /etc/config.scm to add your user and services. Or to boot up into the > installer and

Re: Release v1.2 timetable

2020-10-06 Thread Efraim Flashner
On Tue, Oct 06, 2020 at 09:05:53AM +0200, Mathieu Othacehe wrote: > > Hello Efraim, > > > What's the plan for an installer for the armhf/aarch64 boards? Do we > > want to produce installer images for them or just ensure they work? I > > ran into some issues when I was trying to create an

Re: Release v1.2 timetable

2020-10-06 Thread Mathieu Othacehe
Hello Efraim, > What's the plan for an installer for the armhf/aarch64 boards? Do we > want to produce installer images for them or just ensure they work? I > ran into some issues when I was trying to create an installer for the > beaglebone black. I think that creating installer for those

Re: Release v1.2 timetable

2020-10-06 Thread Efraim Flashner
On Mon, Oct 05, 2020 at 11:17:29PM +0200, zimoun wrote: > Hi, > > On Mon, 5 Oct 2020 at 15:49, Ludovic Courtès wrote: > > > Would be nice! There’s quite a lot of new material to translate now, so > > better leave people time to work on it. > > Do we fix a "deadline"? I mean a (movable) date

Re: Release v1.2 timetable

2020-10-06 Thread Mathieu Othacehe
Hey zimoun, > What is the status of the installer? I don't think there are known issues at the moment. I have started testing it on my laptop, by booting on a flash drive and installing on another one, while being quite anxious for my main hard drive :p. Maybe it would be nice to start a 1.2

Re: Release v1.2 timetable

2020-10-05 Thread zimoun
Hi, On Mon, 5 Oct 2020 at 15:49, Ludovic Courtès wrote: > Would be nice! There’s quite a lot of new material to translate now, so > better leave people time to work on it. Do we fix a "deadline"? I mean a (movable) date as objective for releasing? Initially, I thought about Oct. 29th?

Re: Release v1.2 timetable

2020-10-05 Thread Julien Lepiller
To be clear, translate guix, guix-packages and guix-manual using the TP. Guix-cookbook and guix-website will not be available, so you can translate them directly. Le 5 octobre 2020 08:38:32 GMT-04:00, "Miguel Ángel Arruga Vivas" a écrit : >Hi Julien, > >Julien Lepiller writes: >> I'll try

Re: Release v1.2 timetable

2020-10-05 Thread Ludovic Courtès
Hi, Julien Lepiller skribis: > I'll try sendinq them a tarball for 1.2. Would be nice! There’s quite a lot of new material to translate now, so better leave people time to work on it. > They won't accept new pot files, but maybe they'll update existing > ones. Sure. The website POT files

Re: Release v1.2 timetable

2020-10-05 Thread Miguel Ángel Arruga Vivas
Hi Julien, Julien Lepiller writes: > I'll try sendinq them a tarball for 1.2. They won't accept new pot > files, but maybe they'll update existing ones. Maybe I'm loosing something between all the mail received through this list or on the IRC where I almost never connect to, but why wouldn't

Re: Release v1.2 timetable

2020-10-05 Thread Julien Lepiller
I'll try sendinq them a tarball for 1.2. They won't accept new pot files, but maybe they'll update existing ones. You can push directly whatever is not on the TP. Le 5 octobre 2020 06:18:36 GMT-04:00, "pelzflorian (Florian Pelz)" a écrit : >On Tue, Sep 29, 2020 at 02:16:30PM +0200, zimoun

Re: Release v1.2 timetable

2020-10-05 Thread pelzflorian (Florian Pelz)
On Tue, Sep 29, 2020 at 02:16:30PM +0200, zimoun wrote: > To help the release process, please: > […] > d. translate Julien, shall I just push my translation without going through the TP? Regards, Florian

Re: Release v1.2 timetable

2020-09-29 Thread Danny Milosavljevic
Hi Zimoun, On Tue, 29 Sep 2020 14:16:30 +0200 zimoun wrote: > b. fix bugs severity:important,serious [3,4] or report Bug #43513 means that all armhf substitutes built for armhf on anything else than armhf (especially those built on aarch64) are untrustworthy. I'm working on fixing it (Patch

Release v1.2 timetable

2020-09-29 Thread zimoun
Hi Guixers, The last v1.1.0 had been released [1] a couple of months ago. Since then, a lot of commits with nice features. And new features deserve new release. :-) What do you think if the freeze starts on this Friday Oct., 2nd and the unfreeze as soon as possible? (Ideally less than one