unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Julien Lepiller <julien@lepiller.eu>,
	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 20:36:53 +0100	[thread overview]
Message-ID: <20211218193653.5h5aex5m6wbxq6dc@pelzflorian.localdomain> (raw)
In-Reply-To: <CAJ3okZ0Sa91rtBNxtD4kGG-W6_OWXYhcAM=-Nqa9vhz25AQ1OQ@mail.gmail.com>

Hi simon.

What matters is that users try first to install with the stable Guix
System image, because it is more likely to succeed, but if it does not
succeed, they can try the other one.  In this regard, the terms
stable/latest seem fine to me.  1.3.0/current might reverse the order.

On Sat, Dec 18, 2021 at 04:43:57PM +0100, zimoun wrote:
> However, I have a strong opinion that this label stable/latest is
> confusing, at least in the nav bar.  Especially if you come from other
> distros.  For instance, stable never receives fixes, so it is not
> 'stable' but 'frozen'.

The discussion on IRC provess you right that users get confused.


> Initially, I wanted to replace 'stable' by the current version number;
> something using (latest-guix-version).  I think it is the best: clear
> and easy to translate.  However, I had some hard time with all these
> quote, backquote, unquote, so I gave up. :-)

I agree that the "stable" manual is better described as 1.3.0 (like
what your patch does) and not as stable.  But I am unsure if the
stable manual is needed at all.  You have a more experienced judgment
here though.

Regards,
Florian




  reply	other threads:[~2021-12-18 19:38 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)
2021-12-18 15:43   ` zimoun
2021-12-18 19:36     ` pelzflorian (Florian Pelz) [this message]
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

  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=20211218193653.5h5aex5m6wbxq6dc@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=52596@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --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 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).