From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "\(" <paren@disroot.org>,
59822@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Sat, 07 Jan 2023 08:29:19 +0100 [thread overview]
Message-ID: <87sfgmby5s.fsf@pelzflorian.de> (raw)
In-Reply-To: <87cz7rxojv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 06 Jan 2023 23:53:40 +0100")
Ludovic Courtès <ludo@gnu.org> writes:
> No strong opinion about whether or not to keep “v1.4.0” on the button.
> It nobody objects, we can apply those patches.
Yes. Sorry for ignoring this side issue.
I like knowing the version, but the version is everywhere on the
download page. Renaming the button gives us more options what to put on
the download page. And now the front page translations have to be
adapted anyway because the word advanced is rightfully gone now.
Pushed as a51b8d4cc5a2a1d268edecb2417e728eae8dd2b7, I hope it is OK.
> But then, where would you put the link to /latest?
We could remove the link to latest, but keep the /latest page online
without linking to it, because people have hyperlinks pointing there.
And also move the Hurd and Pinebook Pro image to the regular downloads.
Even though for these, we might want to make releases instead of CI
images? I guess not; also I cannot test Pinebook Pro. I don’t know.
> 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?
The warning is already there and I think it is prominent.
Regards,
Florian
next prev parent reply other threads:[~2023-01-07 7:30 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
2023-01-07 7:29 ` pelzflorian (Florian Pelz) [this message]
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=87sfgmby5s.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=59822@debbugs.gnu.org \
--cc=ludo@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.