List view
- Due by July 2, 2025
- Due by April 9, 2025•1/1 issues closed
- Due by January 15, 2025
- Due by October 23, 2024
- Due by July 17, 2024
- Due by April 10, 2024•5/6 issues closed
- Due by January 17, 2024
- Due by October 25, 2023
- Due by January 18, 2023•2/2 issues closed
- Due by September 28, 2022
- No due date•13/13 issues closed
- No due date•1/1 issues closed
A small release with a lot of internal changes, mostly on Naga side, but not much user-facing.
No due date•3/3 issues closedThis is going to be UUGE
No due date•3/3 issues closed- No due date•2/2 issues closed
https://github.com/gfx-rs/gfx/discussions/3768 has elaborated on the current situation with gfx-rs and wgpu. One of the problems identified there (and affecting our users) is the spread of logic over multiple repositories. Another concern was that `wgpu` goes through a Vulkan-like API that is often an overkill for a target platform, and has too many features. These features (like unaligned copies) become dead weight as the testing doesn't check them. This milestone is about growing this repository to include both the low-level abstraction and the Rust wrapper. It also means `wgpu` will become completely standalone and self-sustainable.
Due by June 18, 2021•3/3 issues closedWe retired this milestone as we are now tracking work via a Github project. Issues that relate to the WebGPU specification (current draft or V1 once it's finalized). Covers the Vulkan/DX12/Metal APIs.
No due date•149/250 issues closed- No due date•3/3 issues closed
- No due date•5/5 issues closed
- No due date•7/7 issues closed
- No due date•6/6 issues closed
- Due by November 3, 2019
Issues that need to be resolved before we integrate wgpu-native into Gecko.
Due by November 14, 2019•8/8 issues closed- No due date•8/8 issues closed