[Mesa-dev] [ANNOUNCE] mesa 19.0.0-rc1

[Dylan Baker]

Quoting Eero Tamminen (2019-02-04 04:41:12)
> Hi,
> 
> On 2.2.2019 3.20, Mark Janes wrote:
> > Eero Tamminen <eero.t.tamminen at intel.com> writes:
> >> On 31.1.2019 1.37, Dylan Baker wrote:
> >>> This email announces the mesa 19.0 release candidate 1. I'll keep this email
> >>> fairly brief since I'm already running a little late on getting this done :)
> >>> I've just had to resolve quite a few autotools issues to get the dist built.
> >>>
> >>> Notable in the 19.0-rc1 branch is SWR is set to require LLVM 7 instead of LLVM
> >>> 6. It is impossible to bootstrap SWR with LLVM 6 and compile with  LLVM 7 due to
> >>> LLVM API changes. Since RadeonSI and Radv both require LLVM 7 I've taken the
> >>> liberty of bumping SWR so that we could get a tarball built.
> >>>
> >>> We've had an exciting release cycle, plenty of GL and Vulkan extensions, ~1600
> >>> commits since the 18.3 branchpoint with substantial work across all areas of
> >>> mesa.
> >>
> >> Are all the recent (i965) perf regressions included to it:
> >> * https://bugs.freedesktop.org/show_bug.cgi?id=109517 (spilling)
> >> * https://bugs.freedesktop.org/show_bug.cgi?id=109505 (Unigine)
> >> * https://bugs.freedesktop.org/show_bug.cgi?id=109216 (Vulkan)
> > 
> > These regressions all need to be added to the release tracker.  Thank
> > you for reporting them.
> 
> If that should track all the things regressed since previous
> 18.3 version was branched:
> -------------------
> tag 18.3-branchpoint
> Tagger: Emil Velikov <emil.l.velikov at gmail.com>
> Date:   Thu Nov 1 18:47:06 2018 +0000
> -------------------
> 
> Then there are a couple of other (i965) regressions I've reported:
> * https://bugs.freedesktop.org/show_bug.cgi?id=109055 (Vulkan / CPU)
> * https://bugs.freedesktop.org/show_bug.cgi?id=108820 (compute hangs)
> * https://bugs.freedesktop.org/show_bug.cgi?id=108787 (BSW CarChase aborts)
> 
> (First two seem at least partially resolved.)
> 
> 
> >> PS. There's also much older:
> >> * https://bugs.freedesktop.org/show_bug.cgi?id=107510
> >>
> >> Which was already fixed, but then regressed again, and regressing commit
> >> wasn't anymore reverted.  I'm mentioning it because Timothy had a patch
> >> series in October that fixed the tess/geom shader regressions (which
> >> were largest), but for some reason it's not yet in upstream.
> 
> That one regressed after 18.2-branchpoint:
> -------------------
> Tagger: Andres Gomez <agomez at igalia.com>
> Date:   Thu Aug 2 17:57:41 2018 +0300
> -------------------
> 
> And it wasn't listed in 18.2.x release tracker bug.
> 
> Neither were its duplicates:
> * https://bugs.freedesktop.org/show_bug.cgi?id=107706
> * https://bugs.freedesktop.org/show_bug.cgi?id=107743
> 
> 
> If there's a release check list for Mesa, it could have items for:
> * having the release tracker meta bug

This is on the list of things to do, but I was in a bit of a time pinch as the
autotools dist target didn't work at all and I needed to get the release out
before leaving the office for the day. That's my bad.

> * going through bugzilla bugs that have been created after previous
>    release branch point was tagged and, adding the relevant ones
>    to the release tracker bug

This has always been the job of each driver team to do. Some drivers don't care
about our releases, other's don't like to use the tracker bug.

Dylan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190206/9eca03d4/attachment.sig>