unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix Devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Shipping more installer images?
Date: Tue, 13 Oct 2020 15:51:19 +0200	[thread overview]
Message-ID: <87y2kai694.fsf@gnu.org> (raw)
In-Reply-To: <20201012154842.71c14e1a@scratchpost.org> (Danny Milosavljevic's message of "Mon, 12 Oct 2020 15:48:42 +0200")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> On Mon, 12 Oct 2020 13:47:25 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Mathieu Othacehe <othacehe@gnu.org> skribis:
>> 
>> Keep in mind that images use space at ftp.gnu.org and also take time to
>> build (having CI up-to-date helps with that, but it doesn’t not
>> eliminate build times due to the ‘update-guix-package’ dance that takes
>> place during “make release”.)
>> 
>> Likewise, if we ship more images, we should update the “System
>> Installation” section accordingly and be clear about what users can
>> expect.
>> 
>> I guess all I’m saying is that we should not make such decisions lightly
>> and be sure to examine all the consequences.
>
> I agree.
>
> IMO there are only very few RYF-worthy ARM devices--and we should support
> at least those, if we support any ARM devices at all.  That includes
> providing images for those few (at least A20-EOMA68, A?0*Olinuxino*, and
> Novena).

So that’s 3 more 1 GiB installer images, right?  If we target Oct. 29th,
how are we going to test them in the meantime?  How long will it take to
build them, even assuming we build on an OverDrive?

I don’t want to spoil the party, I think it’d be great to better support
those devices, but it seems to me that there’s still quite a lot to be
done before we can offer that with reasonable confidence.

Thanks,
Ludo’.


  reply	other threads:[~2020-10-13 13:54 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 12:16 Release v1.2 timetable zimoun
2020-09-29 15:07 ` Danny Milosavljevic
2020-10-07 14:51   ` zimoun
2020-10-07 15:39     ` Danny Milosavljevic
2020-10-07 15:56       ` Weird things found while fixing basic Guix packages Danny Milosavljevic
2020-10-12 11:53         ` Ludovic Courtès
2020-10-07 16:29       ` Release v1.2 timetable Danny Milosavljevic
2020-10-12 11:52       ` 32-bit builds on 64-bit hardware/VMs Ludovic Courtès
2020-10-12 12:06         ` Andreas Enge
2020-10-13 13:54           ` Ludovic Courtès
2020-10-07 16:31     ` Release v1.2 timetable Danny Milosavljevic
2020-10-05 10:18 ` pelzflorian (Florian Pelz)
2020-10-05 11:16   ` Julien Lepiller
2020-10-05 12:38     ` Miguel Ángel Arruga Vivas
2020-10-05 13:50       ` Julien Lepiller
2020-10-05 13:48     ` Ludovic Courtès
2020-10-05 21:17       ` zimoun
2020-10-06  6:57         ` Mathieu Othacehe
2020-10-07 14:36           ` zimoun
2020-10-21  9:14             ` Ludovic Courtès
2020-10-22  7:55               ` Mathieu Othacehe
2020-10-23  8:39               ` zimoun
2020-10-26 22:52                 ` Ludovic Courtès
2020-10-06  6:59         ` Efraim Flashner
2020-10-06  7:05           ` Mathieu Othacehe
2020-10-06  7:26             ` Efraim Flashner
2020-10-06  7:57               ` Mathieu Othacehe
2020-10-07 14:39                 ` zimoun
2020-10-09 18:25                 ` Andreas Enge
2020-10-09 18:37                   ` Danny Milosavljevic
2020-10-12 11:47                 ` Shipping more installer images? Ludovic Courtès
2020-10-12 13:48                   ` Danny Milosavljevic
2020-10-13 13:51                     ` Ludovic Courtès [this message]
2020-10-13 14:19                       ` Mathieu Othacehe
2020-10-13 21:23                         ` Ludovic Courtès
2020-10-13 16:29                       ` Danny Milosavljevic
2020-10-13 15:07                   ` Efraim Flashner
2020-10-13 21:25                     ` Ludovic Courtès
2020-10-19 15:17 ` Update on the timeline for the release v1.2 zimoun
2020-10-19 18:26   ` Miguel Ángel Arruga Vivas
2020-10-19 19:27     ` pelzflorian (Florian Pelz)
2020-10-19 21:57       ` Julien Lepiller
2020-10-21 12:44   ` Ludovic Courtès
2020-10-21 14:14     ` zimoun
2020-10-21 15:57       ` Ludovic Courtès
2020-10-21 18:03         ` Julien Lepiller
2020-10-21 21:27           ` Marius Bakke
2020-10-21 22:16           ` Ludovic Courtès
2020-10-21 22:23             ` zimoun
2020-10-21 22:36             ` zimoun
2020-10-26 22:44               ` Ludovic Courtès
2020-10-31  2:41         ` Maxim Cournoyer
2020-10-31 22:28           ` Branching for v1.2? Ludovic Courtès
2020-11-01  2:21             ` Miguel Ángel Arruga Vivas
2020-11-02 16:56               ` Ludovic Courtès
2020-11-02  8:43             ` zimoun
2020-11-02 13:20               ` Miguel Ángel Arruga Vivas
2020-11-02 15:00                 ` Julien Lepiller
2020-11-02 17:56                   ` pelzflorian (Florian Pelz)
2020-11-03 12:51                     ` Tobias Geerinckx-Rice
2020-11-03 13:46                       ` pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2kai694.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).