[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesa3d-dev
Subject:    Re: Amber branch plan
From:       Adam Jackson <ajax () redhat ! com>
Date:       2022-01-10 19:51:55
Message-ID: CAD_bs+qE1B-etOPtjhQU4ZuBuqosZe18yQmxx-0836Pbd90j0g () mail ! gmail ! com
[Download RAW message or body]

This is my plan as well. I'm aiming to get amber packaged for Fedora
before February so I'll want to see !10557 merged pretty soon.

- ajax

On Mon, Dec 6, 2021 at 7:36 PM Jason Ekstrand <jason@jlekstrand.net> wrote:
>
> +1
>
> On Mon, Dec 6, 2021 at 5:51 PM Dylan Baker <dylan@pnwbakers.com> wrote:
>>
>> 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?
>>
>> Dylan

[prev in list] [next in list] [prev in thread] [next in thread]