all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Florian Paul Schmidt <mista.tapas@gmx.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Refer to GuixSD as beta software
Date: Sun, 17 Apr 2016 16:22:15 +0200	[thread overview]
Message-ID: <877ffwb9ig.fsf@gnu.org> (raw)
In-Reply-To: <5703BDD4.6090903@gmx.net> (Florian Paul Schmidt's message of "Tue, 5 Apr 2016 15:29:56 +0200")

Florian Paul Schmidt <mista.tapas@gmx.net> skribis:

> On 05.04.2016 14:08, Jelle Licht wrote:
>> Although it is mostly me nitpicking, I was installing GuixSD on an old
>> laptop and noticed that the message of the day of the installation image
>> still referred to GuixSD as alpha software.
>> 
>> This patch changes the motd of the installer use the term beta software
>> instead.
>
> Some more nitpicking: I don't know if the Guix project has agreed on the
> semantics on the terms "alpha" and "beta", but the usual definition is
> that in "alpha" software might undergo big unexpected (by the user)
> changes so "so it may BREAK IN UNEXPECTED WAYS." is an appropriate
> warning. In "beta" this kind of breakage should not happen. I.e. "beta"
> usually means that the general state of the software is stable and no
> big breakages are expected, but rather it's a phase of ironing out the
> remaining kinks.

I think that’s mostly where we are when it comes to GuixSD.  Guix itself
is a bit further.

Ludo’.

  parent reply	other threads:[~2016-04-17 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 12:08 [PATCH] Refer to GuixSD as beta software Jelle Licht
2016-04-05 13:29 ` Florian Paul Schmidt
2016-04-05 15:16   ` Jelle Licht
2016-04-17 14:22   ` Ludovic Courtès [this message]
2016-04-05 20:21 ` Leo Famulari
2016-04-17 14:24 ` Ludovic Courtès

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=877ffwb9ig.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mista.tapas@gmx.net \
    /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.