| Message ID | 87pmc1kroh.fsf@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [bug#59822,guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button. | expand |
Hi all. 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. In the past, the Guix System latest install image also got better debugging support, but now a new release with debug features is there, this will not be relevant again. Regards, Florian
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’.
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
Hi, On sam., 07 janv. 2023 at 08:29, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote: > We could remove the link to latest, but keep the /latest page online > without linking to it, because people have hyperlinks pointing there. From my point of view, a webpage without internal links pointing to it is a dead and hidden webpage. > 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. From my point of view, it make clearer to have two separated webpages: one for the well-tested and somehow released and frozen images; another one for development wild images built by CI. Cheers, simon
Simon Tournier <zimon.toutoune@gmail.com> writes: > From my point of view, a webpage without internal links pointing to it > is a dead and hidden webpage. Yes without internal links really is not nice, but despite all that, wouldn’t newcomers feel confused if we present them a choice? Wouldn’t newcomers who download a non-working latest put the blame on GNU Guix? Regards, Florian
diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm index 7b72da8..5bbbd70 100644 --- a/website/apps/base/templates/home.scm +++ b/website/apps/base/templates/home.scm @@ -105,7 +105,7 @@ languages (EDSLs) to " (@ (class "action-box centered-text")) ,(button-big #:label (apply string-append - (C_ "button" `("DOWNLOAD v" ,(latest-guix-version) ""))) + (C_ "button" '("DOWNLOAD"))) #:url (guix-url "download/") #:light #true) " " ; A space for readability in non-CSS browsers. diff --git a/website/apps/download/templates/download.scm b/website/apps/download/templates/download.scm index bcf3cd2..9924917 100644 --- a/website/apps/download/templates/download.scm +++ b/website/apps/download/templates/download.scm @@ -65,7 +65,8 @@ Package manager") #\|) ,(G_ `(a (@ (href ,(gnu-url "software/shepherd"))) "GNU Shepherd")) " init system. Alternately, GNU Guix can be installed as an additional package manager on top of an - installed Linux-based system.")) + installed Linux-based system. The latest development snapshots are available" + ,(G_ `(a (@ (href ,(guix-url "download-latest/"))) "here.")))) (div (@ (class "centered-text"))