[Mesa-dev] [ANNOUNCE] mesa 20.1.0-rc3
Hi all, I'd like to announce the third release candidate for the 20.1 branch, Mesa 20.1.0-rc3. As always, please test it and report any issues you may find to https://gitlab.freedesktop.org/mesa/mesa/issues/new And to help us track issues and merge requests relevant to this branch, please add them to the 20.1.0 release milestone: https://gitlab.freedesktop.org/mesa/mesa/milestones/14 There's a good amount of fixes here, but there are still open issues that we'll need to close before the final release, which is currently planned for the 27th. The next release candidate is scheduled for 7 days from now, on 2020-05-20. Eric --- Andres Gomez (2): gitlab-ci: create always the "results" directory with tracie gitlab-ci: correct tracie behavior with replay errors Arcady Goldmints-Orlov (2): anv: increase minUniformBufferOffsetAlignment to 64 intel/compiler: fix alignment assert in nir_emit_intrinsic Axel Davy (1): gallium/util: Fix leak in the live shader cache Blaž Tomažič (1): radeonsi: Fix omitted flush when moving suballocated texture Daniel Schürmann (1): aco: either copy-propagate or inline create_vector operands Eric Engestrom (4): .pick_status.json: Update to 772b15ad3227e08bb4e18932ac9ecf4c29271160 .pick_status.json: Update to 56f955e4850035d915a2a87e2ebea7fa66ab5e19 .pick_status.json: Update to c1c0cf7a66905e8d7ad506842a41b0ad0c5b10da VERSION: bump to 20.1.0-rc3 Erik Faye-Lund (1): util/os_memory: never use os_memory_debug.h Gert Wollny (1): r600: Fix nir compiler options, i.e. don't lower IO to temps for TESS Ian Romanick (1): nir/algebraic: Optimize ushr of pack_half, not ishr Jordan Justen (3): intel/dev: Split .num_subslices out of GEN12_FEATURES macro intel/dev: Add device info for RKL docs/relnotes/new_features.txt: Add RKL to 20.1 release notes Jose Maria Casanova Crespo (2): v3d: Fix swizzle in DXT3 and DXT5 formats v3d: Include supported DXT formats to enable s3tc/dxt extensions Lionel Landwerlin (1): anv: don't expose VK_INTEL_performance_query without kernel support Liviu Prodea (1): util: Make process_test path compatible with mingw native toolchains Marek Vasut (1): etnaviv: Disable seamless cube map on GC880 Pierre Moreau (1): clover/nir: Check the result of spirv_to_nir Qiang Yu (1): panfrost: don't always build bifrost_compiler Rob Clark (1): freedreno/ir3: fix indirect cb0 load_ubo lowering Samuel Pitoiset (2): aco: fix 64-bit trunc with negative exponents on GFX6 radv: limit the Vulkan version to 1.1 for Android git tag: mesa-20.1.0-rc3 https://mesa.freedesktop.org/archive/mesa-20.1.0-rc3.tar.xz SHA256: c90b75ea34302ebde9b81b87c5642fa864c40fe9c4ad34ce0793170c1413168d mesa-20.1.0-rc3.tar.xz SHA512: 20ec0dbace5eb7b8ed7a9f2deab9621fa2ed9d485fb884af95caf0ce5ae14de25d89d9d7c374f0dc891cb5644096dc8576bfbecfaf1604954176891345884175 mesa-20.1.0-rc3.tar.xz PGP: https://mesa.freedesktop.org/archive/mesa-20.1.0-rc3.tar.xz.sig ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] New Mesa3D.org website proposal
On Wed, 2020-05-13 at 06:43 -0600, Brian Paul wrote: > On 05/13/2020 03:13 AM, Erik Faye-Lund wrote: > > On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote: > > > On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote: > > > > On 05/07/2020 04:33 AM, Erik Faye-Lund wrote: > > > > > Hey Brian > > > > > > > > > > TLDR; are you OK with me moving forward with the rework of > > > > > mesa3d.org? > > > > > > > > Yes... > > > > > > > > > > Cool! We've now set up a repo here: > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fmesa%2Fmesa3d.orgdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=CLd07g8WPm7mbsa3033pnhycK25xPD5%2Bi00V0MJ6TIY%3Dreserved=0 > > > > > > I pushed the bare minimum (ish) there so far, and sent a MR for > > > the > > > importing of the news and article-redirects. This is now being > > > served > > > here: > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmesa.pages.freedesktop.org%2Fmesa3d.org%2Fdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=GmaivI1wH4HR6osRoP%2FINlJm%2FgZ6tgb8HsE1ElVhZNE%3Dreserved=0 > > > > > > > A few updates: > > > > 1. You can now preview the repo with the pending MRs merged here, > > if > > you're interested: > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkusma.pages.freedesktop.org%2Fmesa3d.org%2Fdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=U7cC71x9ql%2FCNXpdNxO2%2But3NAVzDo6S91%2BmevJjMsc%3Dreserved=0 > > > > 2. Some people have been asking me why the website is set up as a > > separate repo rather than a subdirectory inside the main mesa repo. > > > > The quick answer to that is that it seemed more logical that way to > > me. > > The website isn't really tied to the mesa release-schedule, apart > > from > > linking to new releases. It's really its own thing. We might for > > instance want to post updates when other projects in the mesa-group > > cuts a release. So this seems to give us some more freedom. > > > > If someone has good arguments against this, I'm open to changing > > it. > > But this seems like the best option to me. > > I'd really like to keep the Mesa content as part of the main Mesa > repo. > I didn't realize you did that. The website is part of the project > and > it's more convenient to have it all in one place. I agree that for a lot of the content, that's the case. But this is kind of the point here: Some stuff doesn't relate to the code, and those are the things that I've proposed to move out. Right now, the website only contains this: 1. A brief introduction of APIs and drivers 2. News 3. Instructions on how update the website Only 1 is somewhat related to the code, but at a very shallow level, and the information changes on a very slow rate. Keeping this up-to date doesn't seem like a big burden to me. News relate to releases, but not to the state of the code itself. Instructions on how to update the website is website-metainfo, and doesn't relate to the code. Everything else is still in the repo, which will be hosted at docs.mesa3d.org. And I think this is the content that is convenient to update together with the code. So, I don't think there's any real inconvenience introduced here. We should thread carefully in what content we migrate out of the main repository. Having content in the main repository also leads to some issues, like finding the right content for the right release. It can be frustrating to read content that is more up-to-date than the version you're using. This work doesn't solve that right now, but it's taking a step in that direction: We can start versioning the technical documentation, while still allowing people to see up-to-date news. This could easily be finished off by moving docs.mesa3d.org to be hosted at readthedocs.org, which supports multiple versions. I already did a test-intgration of that, and it was trivial, but I didn't like the added ads, so I'm holding off on it for now. But I would very much like to see versioned docs as a future step. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] New Mesa3D.org website proposal
Hi, I'm generally ambivalent on which day it moves, though depending on how late in the day it comes out, it might not actually be Thursday - if the release comes out late at night, I'm more likely to finish up the migration over the weekend. On Wed, 13 May 2020 at 13:43, Brian Paul wrote: > On 05/13/2020 03:13 AM, Erik Faye-Lund wrote: > > 2. Some people have been asking me why the website is set up as a > > separate repo rather than a subdirectory inside the main mesa repo. > > > > The quick answer to that is that it seemed more logical that way to me. > > The website isn't really tied to the mesa release-schedule, apart from > > linking to new releases. It's really its own thing. We might for > > instance want to post updates when other projects in the mesa-group > > cuts a release. So this seems to give us some more freedom. > > > > If someone has good arguments against this, I'm open to changing it. > > But this seems like the best option to me. > > I'd really like to keep the Mesa content as part of the main Mesa repo. > I didn't realize you did that. The website is part of the project and > it's more convenient to have it all in one place. It's a fair point, but then there's the ageing issue with branches. If someone is working against the 19.3.x repo, they'll see a snapshot of the website at a pretty arbitrary point in time - whenever it was that it was forked. That doesn't sound ideal to me, nor does the alternate idea of picking back all the content to all our live branches (e.g. when we do a 20.0.x stable release, cherry-pick the news-page update to 19.3.x?). There's also a circular dependency issue related to publishing releases: it seems odd to commit and tag a release, then have the very next commit be the update to the page, which you can't do in one as you don't know the SHA before you commit. Code information and documentation _definitely_ belongs with the Mesa project though. Things like the Gallium3D documentation published out to ReadTheDocs should be maintained in with the code and generated with the code - and this should be extended through the whole Mesa source tree, so we have much better live docs of our codebase. I've been working with Erik to figure out how we can best get this published alongside the main website. We absolutely shouldn't be putting up any barriers to keeping the website updated and making sure we have good contributions to it, though. I think putting it in a separate repo actually makes it slightly easier if anything, provided that we have a good set of reviewers keeping eyes on it, and clear instructions on how to contribute to it. Cheers, Daniel ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] New Mesa3D.org website proposal
On 05/13/2020 03:13 AM, Erik Faye-Lund wrote: On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote: On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote: On 05/07/2020 04:33 AM, Erik Faye-Lund wrote: Hey Brian TLDR; are you OK with me moving forward with the rework of mesa3d.org? Yes... Cool! We've now set up a repo here: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fmesa%2Fmesa3d.orgdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=CLd07g8WPm7mbsa3033pnhycK25xPD5%2Bi00V0MJ6TIY%3Dreserved=0 I pushed the bare minimum (ish) there so far, and sent a MR for the importing of the news and article-redirects. This is now being served here: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmesa.pages.freedesktop.org%2Fmesa3d.org%2Fdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=GmaivI1wH4HR6osRoP%2FINlJm%2FgZ6tgb8HsE1ElVhZNE%3Dreserved=0 A few updates: 1. You can now preview the repo with the pending MRs merged here, if you're interested: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkusma.pages.freedesktop.org%2Fmesa3d.org%2Fdata=02%7C01%7Cbrianp%40vmware.com%7Cb8ff6d838d46414812f208d7f71df219%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637249580306260765sdata=U7cC71x9ql%2FCNXpdNxO2%2But3NAVzDo6S91%2BmevJjMsc%3Dreserved=0 2. Some people have been asking me why the website is set up as a separate repo rather than a subdirectory inside the main mesa repo. The quick answer to that is that it seemed more logical that way to me. The website isn't really tied to the mesa release-schedule, apart from linking to new releases. It's really its own thing. We might for instance want to post updates when other projects in the mesa-group cuts a release. So this seems to give us some more freedom. If someone has good arguments against this, I'm open to changing it. But this seems like the best option to me. I'd really like to keep the Mesa content as part of the main Mesa repo. I didn't realize you did that. The website is part of the project and it's more convenient to have it all in one place. -Brian ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] New Mesa3D.org website proposal
On Tue, 2020-05-12 at 12:17 +0200, Erik Faye-Lund wrote: > On Thu, 2020-05-07 at 11:03 -0600, Brian Paul wrote: > > On 05/07/2020 04:33 AM, Erik Faye-Lund wrote: > > > Hey Brian > > > > > > TLDR; are you OK with me moving forward with the rework of > > > mesa3d.org? > > > > Yes... > > > > Cool! We've now set up a repo here: > > https://gitlab.freedesktop.org/mesa/mesa3d.org > > I pushed the bare minimum (ish) there so far, and sent a MR for the > importing of the news and article-redirects. This is now being served > here: > > https://mesa.pages.freedesktop.org/mesa3d.org/ > A few updates: 1. You can now preview the repo with the pending MRs merged here, if you're interested: https://kusma.pages.freedesktop.org/mesa3d.org/ 2. Some people have been asking me why the website is set up as a separate repo rather than a subdirectory inside the main mesa repo. The quick answer to that is that it seemed more logical that way to me. The website isn't really tied to the mesa release-schedule, apart from linking to new releases. It's really its own thing. We might for instance want to post updates when other projects in the mesa-group cuts a release. So this seems to give us some more freedom. If someone has good arguments against this, I'm open to changing it. But this seems like the best option to me. 3. Last but not least, I've been discussing deployment timeline with a few stakeholders, and want to hijack this thread for bringing all of these in the loop. As far as I know, what's left to do is: - Set up NGINX redirects for mesa3d.org/archive/* -> archive.mesa3d.org/* - Wait for the go-signal from Mesa release-managers (read below) - Update and merge https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4630 - Update and merge https://gitlab.freedesktop.org/mesa/mesa3d.org/-/merge_requests/5 - Switch over the DNS to point to the GitLab pages host Eric told me that Thursdays would generally be the best option for doing the switch-over, right after cutting a release. This would give us the most time to correct any fallouts until the next release cycle. So, how do people feel about making the switch-over tomorrow? Is that too early? Maybe we should wait at least one more week? Is there anything else I'm missing? ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
