Re: Subversion 1.15.0-rc2 up for testing/signing

Ivan Zhakov <[email protected]>
Newsgroups gmane.comp.version-control.subversion.devel
Message-ID <CAPZho08RqA90rab++f3x6hKCZaOsutVUgh4dTaw0a-2oz4QHYA@mail.gmail.com>
On Wed, 1 Jul 2026 at 18:00, Ivan Zhakov <[email protected]> wrote:

> On Tue, 30 Jun 2026 at 19:19, Daniel Sahlberg <[email protected]>
> wrote:
>
>> Den mån 29 juni 2026 kl 23:38 skrev Branko Čibej <[email protected]>:
>>
>>> 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?
>>>
>>>
>>>
>>> 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.
>>>
>>
>> It seems to be consensus on solution "B" (explicitly enable schema
>> validation) and unless it will take very long to implement, I think we
>> should wait. Maybe @Ivan Zhakov <[email protected]> can chime in here?
>>
>> The `xml-schema-validation-improvements` branch has been merged to trunk
> [1] in r1935776.
>
> Next, I plan to propose this change for backport to 1.15.x. I believe this
> will resolve the issue (2).
>
> This step of the plan is now complete: I created a backport branch, and
the r1935776 change is now nominated for backport to 1.15.x.

-- 
Ivan Zhakov
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.