Hi,
On 2.2.2019 3.20, Mark Janes wrote:
Eero Tamminen <eero.t.tammi...@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.veli...@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 <ago...@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
* 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
- Eero
Expect rc2 about this time next week, see you then.
Dylan
git tag: mesa-19.0.0-rc1
https://mesa.freedesktop.org/archive/mesa-19.0.0-rc1.tar.gz
MD5: b3a610b204d0cb3431823353a8cbe8e6 mesa-19.0.0-rc1.tar.gz
SHA1: d1f0d0bc49ec7e02d0cd7d141127fd2fefc72e35 mesa-19.0.0-rc1.tar.gz
SHA256: 0a14bb059f6cead4e50923df9c24d3c5025d9310803ca5189e019f07e539639e
mesa-19.0.0-rc1.tar.gz
SHA512:
5bedc917afecef6a0dd11c56688a3e3fdbbaeaceca33062d6825b5525c6e78663e873bdecc96b98b0448d988ad81a7a8617c523e2d312384369c6a333b790b86
mesa-19.0.0-rc1.tar.gz
PGP: https://mesa.freedesktop.org/archive/mesa-19.0.0-rc1.tar.gz.sig
https://mesa.freedesktop.org/archive/mesa-19.0.0-rc1.tar.xz
MD5: 727abb6469e518ff1a2e1bde33543503 mesa-19.0.0-rc1.tar.xz
SHA1: 577642259cd269c883007df7c2772c8c636fabfb mesa-19.0.0-rc1.tar.xz
SHA256: 8efb32956c428d23f78364f9eace5491bda9feaafd767128133672a5f79659e8
mesa-19.0.0-rc1.tar.xz
SHA512:
23d21d6c4f03a1d9073ecb1f43dc251d581cdeb6b7cc24a19c299571070b4184ad4f22b0ca170ca42e58c62bb46eca0dadc334a952bbb7e0379961a30a6ca856
mesa-19.0.0-rc1.tar.xz
PGP: https://mesa.freedesktop.org/archive/mesa-19.0.0-rc1.tar.xz.sig
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
