[Mesa-dev] [ANNOUNCE] Mesa 18.2.2 release candidate
Juan A. Suarez Romero
jasuarez at igalia.com
Wed Oct 3 16:43:46 UTC 2018
On Wed, 2018-10-03 at 16:54 +0200, Michel Dänzer wrote:
> On 2018-10-03 2:41 p.m., Juan A. Suarez Romero wrote:
> > Hello list,
> >
> > The candidate for the Mesa 18.2.2 is now available. Currently we have:
> > - 20 queued (+1 squashed)
> > - 2 nominated (outstanding)
> > - and 0 rejected patches
> >
> > The current queue consists of:
> >
> > Different patches for the DirectX9 and DRI state trackers.
> >
> > A patch to implement vkAcquireNextImage2 in the Intel and AMD vulkan drivers, as
> > well as a patch for adding support for protected memory properties in
> > GetPhysicalDeviceProperties2() for the former driver.
> >
> > RADV also gets a patch to fix some issues with reflections in GTA V, and a path
> > to fix a GPU hang in SteamVR with Vega.
> >
> > Finally, there are more fixes for Radeonsi, nvc0, vc4, and vulkan code.
> >
> > Take a look at section "Mesa stable queue" for more information.
> >
> >
> > Testing reports/general approval
> > --------------------------------
> > Any testing reports (or general approval of the state of the branch) will be
> > greatly appreciated.
> >
> > The plan is to have 18.2.2 this Friday (5th October), around or shortly after 10:00
> > GMT.
> >
> > If you have any questions or suggestions - be that about the current patch queue
> > or otherwise, please go ahead.
>
> FYI, https://patchwork.freedesktop.org/patch/254393/ fixes a regression
> (which doesn't seem to affect Gallium based drivers) from 18.2.1. I'm
> not sure which is better: Try getting it into 18.2.2, or give it some
> time to soak in master, and wait for 18.2.3. What do you think?
>
Unless it fixes a very critical problem, I'd wait until it gets landed in
master. That's the procedure.
I think you can ping someone to get it reviewed, telling it fixes a regression
in stable branch, in order to get it in master soon. Hopefully, if this happens
before next 18.2.3 release (in a couple of weeks), we can include it in the
release.
J.A.
More information about the mesa-dev
mailing list