From: Suhail Singh <suhailsingh247@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Suhail Singh" <suhailsingh247@gmail.com>,
"Ricardo Wurmus" <rekado@elephly.net>,
guix-devel@gnu.org, guix-maintainers@gnu.org,
"Cayetano Santos" <csantosb@inventati.org>,
"Efraim Flashner" <efraim@flashner.co.il>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: On the quest for a new release model
Date: Mon, 16 Dec 2024 11:28:54 -0500 [thread overview]
Message-ID: <87y10fsibd.fsf@gmail.com> (raw)
In-Reply-To: <87bjxbu55j.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 16 Dec 2024 22:30:16 +0900")
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> If we can agree that producing a release with lowered expectations is
> better than producing none, I don't mind to get the ball going.
I think it would be helpful to consider our approach for the upcoming
release distinctly from what we choose to do for subsequent releases.
It would help to hear Ludo's thoughts regarding the upcoming release.
> Long term I think I'd like to see for releases:
>
> 1. Simplicity - just a tag, release email, artififact uploads may be
> good enough, if we release often.
>
> 2. Automation - We already have many things automated, but it could be
> polished a bit more (such as a better tool to produce the announcement
> email), and perhaps some way to automatically test that a Guix istalled
> via guix-install.sh' in various environments work (perhaps Docker could
> help with that, having readily minimal images of Debian, Ubuntu, Fedora,
> etc. to run our script on).
>
> 3. Frequency - we want to release often
Agreed on all points, but especially frequency (3). If we aim for that,
feasibility and practicality will encourage 1 and 2.
--
Suhail
next prev parent reply other threads:[~2024-12-16 16:29 UTC|newest]
Thread overview: 65+ 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
2024-12-15 8:44 ` Efraim Flashner
2024-12-15 16:43 ` Ricardo Wurmus
2024-12-15 20:21 ` Suhail Singh
2024-12-15 22:49 ` Ricardo Wurmus
2024-12-15 23:33 ` Suhail Singh
2024-12-16 9:43 ` Efraim Flashner
2024-12-16 13:30 ` Maxim Cournoyer
2024-12-16 16:28 ` Suhail Singh [this message]
2024-12-18 16:48 ` Ludovic Courtès
2024-12-18 17:31 ` Suhail Singh
2024-12-18 17:42 ` Suhail Singh
2024-12-19 17:56 ` Greg Hogan
2024-12-20 12:06 ` Maxim Cournoyer
2024-12-21 13:18 ` Andreas Enge
2024-12-28 17:38 ` Ludovic Courtès
2024-12-29 4:56 ` Maxim Cournoyer
2024-12-20 22:07 ` Thiago Jung Bauermann
2024-12-19 18:03 ` Greg Hogan
2024-12-20 12:17 ` Maxim Cournoyer
2024-12-28 17:43 ` Ludovic Courtès
2024-12-16 10:47 ` pelzflorian (Florian Pelz)
2024-12-16 16:14 ` Ricardo Wurmus
2024-12-18 18:54 ` Vagrant Cascadian
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=87y10fsibd.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=csantosb@inventati.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.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 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).