From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Reflections on the release process Date: Fri, 17 Apr 2020 14:46:03 +0200 Message-ID: References: <873694o674.fsf@inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57941) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPQNy-000221-1u for guix-devel@gnu.org; Fri, 17 Apr 2020 08:46:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jPQNw-0005eU-UC for guix-devel@gnu.org; Fri, 17 Apr 2020 08:46:21 -0400 In-Reply-To: <873694o674.fsf@inria.fr> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel Hi Ludo, Thanks to everyone ! On Wed, 15 Apr 2020 at 22:18, Ludovic Court=C3=A8s wrote: > 4. We lack a clear way to mark bugs as release-critical. I=E2=80=99m rea= lly > happy Florian, Mathieu, and I have been able to work together and squash > bugs one by one (thank you!). Still, it would have been better if we > could have tagged which is release-critical and which is not, to prevent > misunderstandings such as regarding the NVMe bug: > . Can Debbugs help? The GCC > folks have a system that sends email with an update on the number of > release-critical bugs. I=E2=80=99m sure we can learn from how others dea= l with > that. The first easy step seems to tag the relevant bug as release-critical or simply rc. Currently, the tags nomal, security, serious, moreinfo, important, unreproducible are used in Debbugs. Then a second step could be to collect these release critical bugs and display them on issues.guix.gnu.org (or data.guix.gnu.org) for example remplacing the circle exclamation mark by a red triangle exclamation mark (or any really visible symbol). And because the "recent activities" is already sorted, it becomes easier to point the remaining release critical bugs, the ones stuck, etc. > For the other issues, I=E2=80=99m interested in any ideas you may have! About the "frozen" window, does it make to schedule it in advance? For example a couple of months before. And for example, does it make sense to say: at least one release each year on the March 14th (Pi day ;-) or approximately. Because in general FOSDEM is at the beginning of February and it is a big party where some of us come then back home refill of energy, we could agree around this date (beginning of Feb.) on the frozen window date (say end of February) and then release around middle of March. >From my point of view, using the Guix Days as catalyst for releasing should help the process. Cheers, simon