Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.189.118])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 60A7E781AA0
	for <~alpine/devel@lists.alpinelinux.org>; Sun, 17 Nov 2019 20:10:37 +0000 (UTC)
Received: from mx1.tetrasec.net (mail.local [127.0.0.1])
	by mx1.tetrasec.net (Postfix) with ESMTP id 85BB12DE28EE
	for <~alpine/devel@lists.alpinelinux.org>; Sun, 17 Nov 2019 20:10:35 +0000 (UTC)
Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: alpine@tanael.org)
	by mx1.tetrasec.net (Postfix) with ESMTPSA id B9F8B2DE27AC
	for <~alpine/devel@lists.alpinelinux.org>; Sun, 17 Nov 2019 20:10:34 +0000 (UTC)
Date: Sun, 17 Nov 2019 21:10:26 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Alpine develmopment <~alpine/devel@lists.alpinelinux.org>
Subject: 3.11 builders are up / feature freeze
Message-ID: <20191117211026.2504e5bc@ncopa-desktop.copa.dup.pw>
X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-alpine-linux-musl)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi!

As you may have noticed, the builders for v3.11 is up now.

This means that we need to focus on stabilizing what we have in the
tree and close open issues rather than work on adding new things or do
things that delays the release.

We have a freeze on toolchain and build tools. This means packages that
are used to build other packages (gcc, gnu make, cmake, ninja, flex,
bison, abuild etc). Everything that changes the way packages are built
in significant way.

What we want avoid is having the packages successfully built now, but
fails to build when we push security updates or bugfixes in future, due
to some change of the build tools.

We should also be careful with ABI breaking upgrades. I don't mind that
we push upgrades that break ABI as long as it does not creates much
work (and end up delay the release). So ABI breakages is ok if there
are around 5 packages that needs to be rebuilt. If there are many
packages that needs to be rebuilt then we should wait til after v3.11
release unless there are good reasons to include it in v3.11.

I do think that we should try get the 5.4 kernel in as it is an Long
Time Support release[1] and the kernel does not have any significance
on how the packages are built.

It would also be nice to have rpi4 support included. This should not
affect how the packages are built.

We do want the 5.4 (rc?) kernel and rpi4 support in before we do the
first 3.11 release candidate, so we can test it before release.

It would also be nice if we could try fix as many of the bugs/isses in
bug tracker as possible. 

Lets make this release the best release so far!

Thanks!

-nc

[1]: https://www.kernel.org/category/releases.html