[Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened
maraeo at gmail.com
Thu Jan 30 04:20:28 UTC 2020
Feel free to make the branchpoint now. We don't really need to wait for
anybody. Drivers that need fixing can have their fixes backported later.
The longer we wait, the greater the chance that somebody will introduce new
regressions in master.
On Wed, Jan 29, 2020 at 11:02 PM Jason Ekstrand <jason at jlekstrand.net>
> On Wed, Jan 29, 2020 at 4:46 AM Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
>> On Tue, Jan 28, 2020 at 8:46 PM Dylan Baker <dylan at pnwbakers.com> wrote:
>> > Quoting Dylan Baker (2020-01-22 10:27:05)
>> > > Hi list, due to some last minute changes in plan I'll be managing the
>> > > release. The release calendar has been updated, but the gitlab
>> milestone wasn't
>> > > opened. That has been corrected, and is here
>> > > https://gitlab.freedesktop.org/mesa/mesa/-/milestones/9, please add
>> any issues
>> > > or MRs you would like to land before the branchpoint to the milestone.
>> > >
>> > > Thanks,
>> > > Dylan
>> > >
>> > Hi list,
>> > There are still a fair number of issues and MRs opened for the 20.0
>> > point, should we postpone the branch point?
>> IMO we should primarily look at what is needed to be ready in time for
>> the Spring 2020 distro releases* in this release cycle. It doesn't
>> make sense to add a few more features if we're effectively postponing
>> improvements (most of which should already be committed!) getting into
>> the hands of users.
> Scanning through the milestone, !3591 is the only thing on there that
> isn't a bugfix that we would likely want to backport anyway. I don't know
> that we need to hold up the release on all the Gen12 Intel fixes. We can
> back-port them if we want.
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mesa-dev