Amber branch plan

Dylan Baker dylan at
Mon Dec 6 23:51:08 UTC 2021

Since classic is gone,  I thought I'd lay out my thinking for Amber.

I'm assuming that we'll branch Amber from the 21.3 branch, after that
reaches normal EOL. That gives us the benefit of developing on top of a
known good state for classic drivers, and should minimize friction for
distros dealing with classic. If anyone wants to backport changes from
main to amber they can obviously do so.

Are there any objections to that plan?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <>

More information about the mesa-dev mailing list