all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>,
	52596@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#52596] [guix-artwork PATCH] website: Relabel stable/latest to release/current.
Date: Sat, 18 Dec 2021 16:22:17 +0100	[thread overview]
Message-ID: <20211218152217.l5vtbwkwhmiwuzfe@pelzflorian.localdomain> (raw)
In-Reply-To: <20211218104038.306475-1-zimon.toutoune@gmail.com>

Hello simon.  Thank you for the patch, even though I disagree.

On Sat, Dec 18, 2021 at 11:40:38AM +0100, zimoun wrote:
> This discussion [1] points that the current label stable/latest for:
> 
>  - things related to release
>  - things related to current master
> 
> is confusing.  Mainly because 'stable' has other meaning in other distro.
> Moreover, 'latest' does not imply less stable or buggy than 'stable' itself.
> 
> Instead, the label 'release/current' appears to be more accurate for a
> rolling-release.
> 
> WDYT?
> 
> 1: <http://logs.guix.gnu.org/guix/2021-12-17.log#201813>

The term 'release' seems technical and hard-to-translate.  Stable may
raise wrong expectations, but one word cannot convey all the
difference between the images anyway.  I think the criticism of our QA
is too negative, even though more QA would have been better.

However there are few reasons to read the stable manual.  Hmm.

> diff --git a/website/apps/base/templates/help.scm b/website/apps/base/templates/help.scm
> index 3d54ae1..fb25bd5 100644
> --- a/website/apps/base/templates/help.scm
> +++ b/website/apps/base/templates/help.scm
> @@ -51,7 +51,7 @@ system|GNU Hurd|GNU Guix package manager|Help resources") #\|)
>              online.  You may also find more information about Guix by running "
>              ,(G_ `(code "info guix")) "."))
>          (p
> -         ,(link-more #:label (G_ "Read stable manual")
> +         ,(link-more #:label `(G_ "Read manual " ,(latest-guix-version) "")

This should be

,(link-more #:label (G_ (string-append "Read manual " (latest-guix-version) "")))

with string-append like further below for

     ,(G_ (string-append "Page " (number->string active-page) " of "
                         (number->string pages) ". Go to another page: ")))


>           ,(link-more #:label (G_ "Read latest manual")
>                       #:url (guix-url "manual/devel/" #:localize #f))))
> diff --git a/website/apps/download/templates/download-latest.scm b/website/apps/download/templates/download-latest.scm
> [...]
>     #:content
>     `(main
>       (section
>        (@ (class "page"))
> -      ,(G_ `(h2 "Download latest images"))
> +      ,(G_ `(h2 "Download latest developement images"))

There is a typo, but more importantly the meaning of development
images is hard to understand.

This is a difficult topic. ;)

Regards,
Florian




  reply	other threads:[~2021-12-18 15:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-18 10:40 [bug#52596] [guix-artwork PATCH] website: Relabel stable/latest to release/current zimoun
2021-12-18 15:22 ` pelzflorian (Florian Pelz) [this message]
2021-12-18 15:43   ` zimoun
2021-12-18 19:36     ` pelzflorian (Florian Pelz)
2021-12-19  9:21       ` zimoun
2021-12-19 10:40         ` pelzflorian (Florian Pelz)
2021-12-23  1:21           ` pelzflorian (Florian Pelz)
2021-12-24 17:34         ` pelzflorian (Florian Pelz)
2021-12-29 16:40           ` zimoun
2021-12-29 19:42             ` pelzflorian (Florian Pelz)
2021-12-29 20:07               ` Leo Famulari
2021-12-29 22:53                 ` pelzflorian (Florian Pelz)
2021-12-30 15:49                   ` zimoun
2021-12-30 17:03                     ` pelzflorian (Florian Pelz)
2021-12-29 20:07               ` zimoun

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=20211218152217.l5vtbwkwhmiwuzfe@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=52596@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=me@tobias.gr \
    --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.