unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
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, 30 Dec 2022 13:21:50 +0100	[thread overview]
Message-ID: <87pmc1kroh.fsf@gmail.com> (raw)
In-Reply-To: <87r0ws50yl.fsf_-_@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

Hi,

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/>.


> The release process is not just ceremonial; over the last couple of
> months, we’ve put a lot of effort actually fixing things, in particular
> in the installer.  Releases make sense IMO.

Yes, for sure!  Release makes sense.  I do not think someone is
advocating for removing the release itself. :-)

From my understanding, the patch is about discoverability of the latest
Download webpage; this one: <https://guix.gnu.org/en/download/latest/>.

I am still missing why from the Standard download webpage
<https://guix.gnu.org/en/download/>, the mention to the Latest download
webpage would be detrimental or confusing.


[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 1365 bytes --]

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"))

[-- Attachment #3: Type: text/plain, Size: 19 bytes --]


Cheers,
simon





  reply	other threads:[~2022-12-30 14:59 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 [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87pmc1kroh.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59822@debbugs.gnu.org \
    --cc=ludo@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).