all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
	"(" <paren@disroot.org>
Cc: 59822@debbugs.gnu.org
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Thu, 08 Dec 2022 19:10:33 +0100	[thread overview]
Message-ID: <86y1rhg412.fsf@gmail.com> (raw)
In-Reply-To: <87y1rhzvxz.fsf@pelzflorian.de>

Hi Florian, all,

On Thu, 08 Dec 2022 at 17:44, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:

> CI images are for developers and testers.  The standard installer did
> not get bug fixes in the 1.3.0 period, but it can and should.  It is
> possible to put up a new installer without a new Guix release.

I do not want to bother more but this paragraph suggests an other
direction. :-)

The front page <https://guix.gnu.org/> contains the explicit version
number with the button «Download v1.3.0».  Why not, just remove this
version label and just have the button «Download»?

This button «Download» leads to «https://guix.gnu.org/en/download/».
Here, we could do the same as we do for the package guix, for instance
use the version label 1.3.0-8.abc123 for some images.

However, it means that we need to update <https://ftp.gnu.org/gnu/guix/>
each time the recommended standard installer or other receives important
fixes.  It does not happen that much often. :-)

Well, I mean being able to update independently some images of «GNU Guix
binary» and «GNU Guix System» without going to the big dance of a
complete release.

Obviously, we could have more frequent releases; which would fix most of
the issue. :-) But, we do not have.  Somehow being able to update the
standard downloadable installer without creating a new release appears
to me a good solution.

In addition to Ludo, who has the power to upload (and sign) the images
to <https://ftp.gnu.org/gnu/guix/>?


Cheers,
simon




  parent reply	other threads:[~2022-12-08 18:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 19:50 [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button ( via Guix-patches via
2022-12-04 21:50 ` pelzflorian (Florian Pelz)
2022-12-04 21:58   ` pelzflorian (Florian Pelz)
2022-12-04 22:03     ` pelzflorian (Florian Pelz)
2022-12-05  7:02       ` ( via Guix-patches via
2022-12-05  8:00         ` pelzflorian (Florian Pelz)
2022-12-05  9:00           ` zimoun
2022-12-05 17:06             ` pelzflorian (Florian Pelz)
2022-12-05 17:41               ` pelzflorian (Florian Pelz)
2022-12-06 11:22               ` zimoun
2022-12-06 16:33                 ` pelzflorian (Florian Pelz)
2022-12-06 17:45                   ` zimoun
2022-12-07 14:26                     ` pelzflorian (Florian Pelz)
2022-12-08  9:36                       ` pelzflorian (Florian Pelz)
2022-12-08 10:12                         ` zimoun
2022-12-08 11:50                           ` bug#59822: " pelzflorian (Florian Pelz)
2022-12-08 15:49                             ` [bug#59822] " ( via Guix-patches via
2022-12-05 16:51           ` ( via Guix-patches via
2022-12-08 16:44             ` pelzflorian (Florian Pelz)
2022-12-08 16:46               ` ( via Guix-patches via
2022-12-08 18:10               ` zimoun [this message]
2022-12-08 19:44                 ` pelzflorian (Florian Pelz)
2022-12-21 13:40                 ` Ludovic Courtès
2022-12-30 12:21                   ` zimoun
2022-12-31 15:43                     ` pelzflorian (Florian Pelz)
2023-01-06 22:53                     ` Ludovic Courtès
2023-01-07  7:29                       ` pelzflorian (Florian Pelz)
2023-01-09 10:13                         ` Simon Tournier
2023-01-09 19:35                           ` pelzflorian (Florian Pelz)
2023-01-11 16:11                             ` Simon Tournier
2023-01-12 17:56                               ` pelzflorian (Florian Pelz)
2022-12-05  7:01   ` ( via Guix-patches via

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

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

  git send-email \
    --in-reply-to=86y1rhg412.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59822@debbugs.gnu.org \
    --cc=paren@disroot.org \
    --cc=pelzflorian@pelzflorian.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.