DomainKey-Signature: a=rsa-sha1; c=nofws; d=soeren-tempel.net; h=date:to
	:subject:from:references:in-reply-to:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=opensmtpd; b=C
	dGQfmrMcSXaopHvfJpfYu6zuEGrRE+b5cuk+DCUnmSDjqDry60aPjyzReApADjMO
	5fBd1oLxoOS0Px8fQD7EKSdEe+bcKq+j+E1FnxU0T4P7stvx4re2ky5zMmNC1Non
	VssircnI+rhK7b/u1iPwGRVkAqUX45Q+dj3j29nOEc=
Date: Sat, 30 May 2020 11:11:42 +0200
To: ~alpine/devel@lists.alpinelinux.org
Subject: Re: release qualification process
From: =?UTF-8?Q?S=C3=B6ren?= Tempel <soeren@soeren-tempel.net>
References: <15782174.Tt3s28fcIf@localhost>
In-Reply-To: <15782174.Tt3s28fcIf@localhost>
Message-Id: <3ICP52XPGB00H.3TPAWIW7GLV4P@8pit.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101
 Thunderbird/55.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ariadne Conill <ariadne@dereferenced.org> wrote:
> Hello,

Hi,

> I would like to propose an update to our release qualification process th=
at=20
> should resolve this problem: each architecture has a designated release=20=

> manager, and each release manager gives a go/no-go before the release pro=
cess=20
> 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 architec=
ture=20
> not included in the release, depending on the situation.  The core team (=
or=20
> its designated replacement) may also issue a no-go for a specific archite=
cture.

In general, it would be convenient to have an individual or a group of
individuals "responsible" for a specific architecture. For instance, if
tests for an aport fail on a specific architecture one can contact the
individual(s) responsible for this architecture for further
investigation. Given the amount of architectures we currently support, I
occasionally run into issues on architecture I do not have direct access
to (e.g. s390x) without any means of debugging the issue. The
individual(s) could also be responsible for overseeing the release
process on this architecture.

Greetings,
S=C3=B6ren