On Mon, Jun 29, 2026 at 11:38 PM Branko Čibej <[email protected]> wrote:
> On 29. 6. 2026 20:48, Evgeny Kotkov via dev wrote: > > Evgeny Kotkov <[email protected]> <[email protected]> > writes: > > [...] > > 2) The venv-related issues when running the test suite on Windows. > > Based on the description, this appears to be a regression from 1.14.5. > > Work and discussion on this topic are still ongoing on the ^/branches/ > xml-schema-validation-improvements/ branch. > > [...] > > That leaves (2) as the only remaining item. > > From the RM perspective, I'd lean toward reverting the XML schema validation > from the 1.15.x branch so we can roll RC3, and finalizing the validation > work on trunk on its own schedule. > > Thoughts on this? > > > I think it would be a lot better to try to make a release with the functionality we're certain is safe to include in a new release. I can't say that about the XML schema validation. If the branch fixes some concerns that we had doesn't mean we won't have more issues with it. I suggest we remove it completely and instead roll it in 1.16. Already the entire community spent a lot of effort to "fix" this functionality. This is an indicator that it's not ready for a release. I suggest we revert it completely and go with what Evgeny proposes. > > As far as I'm aware, that branch is essentially done. Leaving this out > again will mean another N years of not validating XML output in the tests > of a published release. > We also didn't have a minor release in more than 5 years. Which is far more important than verifying XML schemas. Also since we already do that in the trunk I don't think it's worth it. I also still believe there might be that time when we can have a more consistent and frequent release cycle in which this isn't a big deal... The more stuff we have in the trunk the faster we have 1.16. Otherwise I could also complain about utf8-cmdline and we'd never have it out. -- Timofei Zhakov
