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

Hi,

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.

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.

[...]

> In addition to Ludo, who has the power to upload (and sign) the images
> to <https://ftp.gnu.org/gnu/guix/>?

The process to be authorized to upload files to ftp.gnu.org and
alpha.gnu.org is described in the GNU Maintainers Guide (info
"(maintain) Automated FTP Uploads").  Maintainers can ask GNU sysadmins
to add specific people to the list of authorized uploaders.

Currently, I believe Ricardo, Maxim, Mathieu, and myself are authorized.
We’ll make sure the next release team is authorized too!

Ludo’.




  parent reply	other threads:[~2022-12-21 13:41 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 [this message]
2022-12-30 12:21                   ` zimoun
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=87r0ws50yl.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=59822@debbugs.gnu.org \
    --cc=paren@disroot.org \
    --cc=pelzflorian@pelzflorian.de \
    --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).