Date: Mon, 30 Mar 2020 12:14:03 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: ~Alpine develmopment <~alpine/devel@lists.alpinelinux.org>
Subject: Planning for 3.12 feature freeze
Message-ID: <20200330121403.71f8e7f9@ncopa-desktop.copa.dup.pw>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi!

In a week or two I will start work on setting up the 3.12 builders.
Once those are up and running we have a feature freeze, which means we
should avoid add new features and focus on fixing the current issues.

Once we have the builder up, we should avoid do significant changes in
toolchains and dependencies that influences how packages are built. For example:

 - abuild
 - gcc
 - linux-headers
 - binutils
 - go
 - llvm/clang
 - rust

If those (or similar packages) needs to be bumped to new major version,
now is the time to do so.

I have already bumped gcc to 9.3 and binutils to 2.34, and I plan to
tag a new release of abuild before the freeze.

Other things that I'd like to have fixed for the 3.12 release:
 - fix aarch64 crystal with newer llvm[1]
 - go default linking[2]

I would also like to fix rust triples to be consistent[3].

Are there other things that should be prioritized before the feature freeze?


[1]: https://gitlab.alpinelinux.org/alpine/aports/issues/11017
[2]: https://gitlab.alpinelinux.org/alpine/aports/issues/11260
[3]: https://gitlab.alpinelinux.org/alpine/aports/issues/11349