unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cayetano Santos <csantosb@inventati.org>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: Greg Hogan <code@greghogan.com>,
	 Ricardo Wurmus <rekado@elephly.net>,
	guix-devel@gnu.org
Subject: Re: On the quest for a new release model
Date: Fri, 13 Dec 2024 21:34:54 +0100	[thread overview]
Message-ID: <87jzc3midt.fsf@inventati.org> (raw)
In-Reply-To: <87cyhvbit6.fsf@gmail.com> (Suhail Singh's message of "Fri, 13 Dec 2024 12:21:09 -0500")

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]


>ven. 13 déc. 2024 at 12:21, Suhail Singh <suhailsingh247@gmail.com> wrote:

> Is my understanding of your scenario as summarized below correct, could
> you please confirm?
>
> There are some individuals who would be able to follow the instructions
> to install Guix.  However, these individuals wouldn't understand the
> instructions to perform a "guix pull".  Further, the number of such
> individuals is greater than zero, and you are proposing that we consider
> their needs when determining the release process for Guix.

Correct. Except the number of such individuals is huge. Some are doing
research, and they don’t need any more complexity, that they see as an
extra overload : they’ll install guix, and start using it. That’s it.
The more it becomes complex, the less they’ll be prone to try.

> Assuming my understanding above is correct, wouldn't you agree that
> (even) for those individuals what's most important is that there is a
> _stable_ and _not-very-outdated_ release available?

Correct again. At least, on a first contact with guix: one release every
4 months, for example, means using on average a two months out to date
guix, which is fine.

Take julia, for example. The cycle is : install guix, check julia,
outdated, forget guix and use julia installer.

> My (and I believe Greg's) contention is that following a time-based
> release process achieves these objectives more effectively than
> following a feature-based release process.

I’m not against: higher instances decide. Anything, but a 2 years old release.

Once again: sure, anything can be done, but it takes time and skills.
And guix is already good and useful enough for most people to use it
smoothly on a daily basis, solving lots of real life problems. Once they
fall into the rabbit hole, they’ll pull substitutes from channels.

But we need releases, first.

--
Cayetano Santos
GnuPG Key:   https://meta.sr.ht/~csantosb.pgp
FingerPrint: CCB8 1842 F9D7 058E CD67 377A BF5C DF4D F6BF 6682

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2024-12-13 20:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 12:19 Discussion notes on releases and branches Andreas Enge
2023-02-12 21:13 ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Josselin Poiret
2023-02-12 21:34   ` Andreas Enge
2023-02-13  9:32   ` Time for RFC? (was Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)) zimoun
2023-02-13 14:07   ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Andreas Enge
2023-02-14 19:12     ` Leo Famulari
2023-02-13  9:22 ` Release (was " Simon Tournier
2023-02-14 10:14 ` Rust team branch " Efraim Flashner
2023-02-14 16:36   ` Rust team branch Andreas Enge
2023-02-14 20:07     ` Efraim Flashner
2023-02-16 10:56       ` Andreas Enge
2023-02-14 16:36   ` Rust team branch (was Re: Discussion notes on releases and branches) Katherine Cox-Buday
2023-02-14 20:08     ` Efraim Flashner
2023-02-15 17:49       ` Katherine Cox-Buday
2023-03-17 15:24 ` Discussion notes on releases and branches Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-18 17:42   ` Leo Famulari
2024-12-13  8:37 ` On the quest for a new release model (was: Discussion notes on releases and branches) Cayetano Santos
2024-12-13 12:03   ` On the quest for a new release model Ricardo Wurmus
2024-12-13 13:01     ` Suhail Singh
2024-12-13 15:21       ` Greg Hogan
2024-12-13 15:52         ` Suhail Singh
2024-12-13 16:05           ` Suhail Singh
2024-12-13 16:28           ` Cayetano Santos
2024-12-13 17:21             ` Suhail Singh
2024-12-13 20:34               ` Cayetano Santos [this message]
2024-12-13 22:13               ` Ricardo Wurmus
2024-12-13 22:27                 ` Suhail Singh
2024-12-13 23:08                 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-12-14  1:38                   ` John Kehayias via Development of GNU Guix and the GNU System distribution.
2024-12-13 16:04   ` Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2024-12-13 17:47     ` Suhail Singh
2024-12-13 20:14       ` Tomas Volf
2024-12-13 22:13         ` Suhail Singh

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=87jzc3midt.fsf@inventati.org \
    --to=csantosb@inventati.org \
    --cc=code@greghogan.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    --cc=suhailsingh247@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).