From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "(" <paren@disroot.org>
Cc: 59822@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Thu, 08 Dec 2022 17:44:56 +0100 [thread overview]
Message-ID: <87y1rhzvxz.fsf@pelzflorian.de> (raw)
In-Reply-To: <COU1FBLY97M0.2YE4BXVWNT9MA@guix-framework> (paren@disroot.org's message of "Mon, 05 Dec 2022 16:51:09 +0000")
"(" <paren@disroot.org> writes:
> On Mon Dec 5, 2022 at 8:00 AM GMT, pelzflorian (Florian Pelz) wrote:
>> With prominent links to 1.3.0 and to the latest version, users might
>> think, of course they want latest. The 1.3.0 version got QA testing and
>> is more likely to not get broken, even though latest might work on newer
>> hardware.
>
> Yes, I thought of this possibility. How about "Download nightly" instead?
> -- (
Reopen. Dust hasn’t set yet on the issue.
Sorry I have read but not responded directly. In my view, the word
nightly would be less understandable than latest, for better or worse.
But recommending CI images still collides a good user experience.
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.
Regards,
Florian
next prev parent reply other threads:[~2022-12-08 16:46 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) [this message]
2022-12-08 16:46 ` ( via Guix-patches via
2022-12-08 18:10 ` zimoun
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=87y1rhzvxz.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=59822@debbugs.gnu.org \
--cc=paren@disroot.org \
--cc=zimon.toutoune@gmail.com \
/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.