unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
	Suhail Singh <suhailsingh247@gmail.com>,
	Cayetano Santos <csantosb@inventati.org>,
	Greg Hogan <code@greghogan.com>,
	guix-devel@gnu.org
Subject: Re: On the quest for a new release model
Date: Sat, 14 Dec 2024 20:53:26 +0000	[thread overview]
Message-ID: <WGHRB2dbA5dNn7BGkIwCM3ZqT0tPVlTb7J5JApTJIMthPOJz3VeEknJkCHEnH9cypus-bGOFYUZo8oSQkz_svwtjpSrOAOJpctC4fh6DHuY=@lendvai.name> (raw)
In-Reply-To: <87ed2bkwpz.fsf@lease-up.com>

> Our releases should mean something.

one thing i haven't seen mentioned:

AFAIU, not any version of guix can pull and build another guix version. i.e. when the guix command gets a new feature that is then used in the code that pulls and builds itself, then we have a bootstrap/staging problem not unlike with self-hosting compilers.

compilers usually use versioned releases to also mark the stages where stage n-1 is guaranteed to be able to build stage n.

i'm not sure how it is currently handled in guix. actually, i cannot come up with an example right now that requires bootstrapping, nor do i know how guix time-machine handles this. i assume everything around the pulling and building infrastructure is kept backwards compatible, so going back in time is not an issue.

but i do seem to remember a case where pulling from an old enough guix requires manual staging with `guix pull --commit=v1.2.3` to avoid pulling in too fresh commits that the current guix command wouldn't be able to build.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The nation that will insist on drawing a broad line of demarcation between the fighting man and the thinking man is liable to find its fighting done by fools and its thinking done by cowards.”
	— Sir William Francis Butler (1838–1910)



  parent reply	other threads:[~2024-12-14 20:54 UTC|newest]

Thread overview: 42+ 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
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-14 17:18                     ` kiasoc5
2024-12-14 18:00                     ` Cayetano Santos
2024-12-14 20:53                   ` Attila Lendvai [this message]
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
2024-12-14  8:59           ` Ricardo Wurmus
2024-12-14 14:23             ` Suhail Singh
2024-12-14 12:26           ` Tomas Volf
2024-12-14 14:49             ` Suhail Singh
2024-12-14  8:53     ` Ricardo Wurmus
2024-12-14 17:21       ` Splitting up Guix channel (was: On the quest for a new release model) 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='WGHRB2dbA5dNn7BGkIwCM3ZqT0tPVlTb7J5JApTJIMthPOJz3VeEknJkCHEnH9cypus-bGOFYUZo8oSQkz_svwtjpSrOAOJpctC4fh6DHuY=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=code@greghogan.com \
    --cc=csantosb@inventati.org \
    --cc=felix.lechner@lease-up.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).