Received: from out1.migadu.com (out1.migadu.com [91.121.223.63])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 0D59B782B1E
	for <~alpine/devel@lists.alpinelinux.org>; Fri, 29 May 2020 17:31:39 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org;
	s=default; t=1590773498;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=57u4b/PYWeI5YHfokkXQlqZUUXuc+hy0gTxteazuczo=;
	b=shuOGSNnqqo5NqH6jjSMAabh0EBVxRjf1QDI2m5966aUqb4Z3a7vYUZayxWrruZcFxkzcN
	he0rf6iCMMqTJ/PJhxX48M6byPy13gHi71kzq+RhlcvppaPWvm71KGItlwibqD8j5aYFJR
	KzTzsFcLXC6ojRfB15jqlaYMcNRoIq0=
From: Ariadne Conill <ariadne@dereferenced.org>
To: ~alpine/devel@lists.alpinelinux.org
Subject: release qualification process
Date: Fri, 29 May 2020 11:31:33 -0600
Message-ID: <15782174.Tt3s28fcIf@localhost>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.90

Hello,

In the process of releasing Alpine 3.12, it was observed that the s390x 
machines had not built any of the RCs and were in fact behind by 22 days.  
This has caused some turbulence in releasing Alpine 3.12, as we are now 
waiting on the s390x builder to catch up.

I would like to propose an update to our release qualification process that 
should resolve this problem: each architecture has a designated release 
manager, and each release manager gives a go/no-go before the release process 
is initiated with a git tag.  In the event that a release manager gives a no-
go for an architecture, the release may either be delayed or the architecture 
not included in the release, depending on the situation.  The core team (or 
its designated replacement) may also issue a no-go for a specific architecture.

Thoughts?

Ariadne