From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "\(" <paren@disroot.org>,
"pelzflorian \(Florian Pelz\)" <pelzflorian@pelzflorian.de>,
59822@debbugs.gnu.org
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Fri, 06 Jan 2023 23:53:40 +0100 [thread overview]
Message-ID: <87cz7rxojv.fsf@gnu.org> (raw)
In-Reply-To: <87pmc1kroh.fsf@gmail.com> (zimoun's message of "Fri, 30 Dec 2022 13:21:50 +0100")
Hello!
zimoun <zimon.toutoune@gmail.com> skribis:
> On Wed, 21 Dec 2022 at 14:40, Ludovic Courtès <ludo@gnu.org> wrote:
>> zimoun <zimon.toutoune@gmail.com> skribis:
>>
>>> 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»?
>>
>> Because people would be downloading the snapshot of the day, for which
>> we haven’t done as much testing as during a regular release process.
>
> I do not see why just the button «Download» instead of the button
> «Download v1.4.0» would lead to people downloading something else than
> the link, i.e., the webpage named <https://guix.gnu.org/en/download/>.
Oh sorry, I had totally misunderstood. :-)
No strong opinion about whether or not to keep “v1.4.0” on the button.
It nobody objects, we can apply those patches.
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> Making latest more discoverable would be unlikely to make it used
> exactly by the select few in need of its features.
>
> Probably we better remove latest from the top menu?
>
> I wouldn’t want newcomers to go for latest because hey, it’s displayed
> prominently and newer. The installation routine for the latest
> installer image also may break. Or after installation, some software is
> broken. Which would mean the initial install is broken, and no
> roll-back is available.
Yes, I agree. But then, where would you put the link to /latest?
Or maybe we can keep it in the menu but add a prominent warning on the
page stating that these are snapshots that haven’t seen as much QA?
Ludo’.
next prev parent reply other threads:[~2023-01-06 22:54 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
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 [this message]
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=87cz7rxojv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59822@debbugs.gnu.org \
--cc=paren@disroot.org \
--cc=pelzflorian@pelzflorian.de \
--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.