From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Leo Famulari <leo@famulari.name>
Cc: Julien Lepiller <julien@lepiller.eu>,
Tobias Geerinckx-Rice <me@tobias.gr>,
52596@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#52596] [guix-artwork PATCH] website: Relabel stable/latest to release/current.
Date: Wed, 29 Dec 2021 23:53:21 +0100 [thread overview]
Message-ID: <20211229225313.ypt3aythgqj5hbpj@pelzflorian.localdomain> (raw)
In-Reply-To: <Ycy/7slyu6s2/KzV@jasmine.lan>
On Wed, Dec 29, 2021 at 03:07:10PM -0500, Leo Famulari wrote:
> On Wed, Dec 29, 2021 at 08:42:57PM +0100, pelzflorian (Florian Pelz) wrote:
> > The only downside to naming it 1.3.0 that I see is that the
> > guix.gnu.org/manual URL will change away from 1.3.0 on the next
> > release.
> Maybe we can paremeterize the responsible code so that it's updated
> automatically?
Leo, we could create https://guix.gnu.org/manual/1.3.0/ and make the
navbar’s Help/GNU Guix Manual 1.3.0 point to
https://guix.gnu.org/manual/1.3.0/ so the meaning of the URL will not
change in the future. This is what I meant; I had expressed myself
badly so I’m unsure now if you really mean that.
It is all unnecessary, I think; IMHO we do not even need both
https://guix.gnu.org/manual/ and https://guix.gnu.org/manual/devel/,
except when users manually change /etc/config.scm without guix pull.
Or do foreign distro users need the old manual to install? But why?
The label Help/GNU Guix Manual 1.3.0 already uses
(define latest-guix-version
(make-parameter "1.3.0"))
so the label will automatically become Help/GNU Guix Manual 1.4.0 or
whatever the next release will be called.
Regards,
Florian
next prev parent reply other threads:[~2021-12-29 22:56 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)
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) [this message]
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=20211229225313.ypt3aythgqj5hbpj@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 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.