Hi all,
The targetted release date for vkd3d 1.9 is four weeks from now, on September 20. That means the development branch will become increasingly frozen as we're nearing the release date.
If you're an upstream vkd3d developer, please do the following:
- Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify all the vkd3d tests pass on your hardware. - Review and improve the documentation. - Apply your best judgment about which patches are appropriate for the current stage of the release process.
Note that it's entirely appropriate to queue up more complicated changes for application post 1.9 and ask for review on them, but please either mark those as draft or put some kind of note in the MR description.
If you're a downstream user of vkd3d, please test your applications for regressions, and file bug reports if you find any. If you're the maintainer of a Wine module that (indirectly) depends on vkd3d, like e.g. d2d1, d3dx9, d3dcompiler, or any of the core Direct3D modules, that includes making sure the unit tests still pass with the new version. We try our best to avoid regressions, but ultimately we depend on our downstream users to catch anything we may have missed before the final release.
The planned release date for the release following vkd3d 1.9 is currently sometime in December.
Regards,
Henri