Evgeny Kotkov <[email protected]> writes:
> With that in mind, I'm inclined to proceed with the following plan: wait until
> the r1935776 change is merged to 1.15.x, and roll RC3 shortly after that.
> I also plan to cast my own vote on the nomination, if time permits.
A quick status update. The XML validation nomination is currently one vote
short of being merged:
* r1935776
Rework XML output validation in tests.
Justification:
Support testing with embeddable Python that doesn't provide 'venv'.
Branch:
1.15.x-r1935776
Votes:
+1: ivan, kotkov
Two other nominations are also just one +1 short of merging:
* r1933386, r1933394, r1933404
Corectness fixes in svn_subr__win32_xlate_to_stringbuf().
Justification:
Fix potential integer overflow.
Votes:
+1: ivan, kotkov
+0: brane (review only, can't test)
* r1934437, r1934438, r1934443, r1934444
Make `svn --version -v` report actual character encoding used on Windows.
Justification:
Makes the reported information correct with respect to the actually used
character encoding on Windows (as per win32_xlate).
Notes:
- Character encoding information was added to `svn --version -v` in
1.15.x.
- This changes behavior when "Beta: Use Unicode UTF-8 for worldwide
support" option is used on Windows.
Votes:
+1: ivan, kotkov
+0: brane (review only, can't test)
Once the XML validation change has its final vote, I'll be able to roll RC3.
But the two other nominations look like low-hanging fruit as well, so it
would be nice to get them merged too.
Thanks,
Evgeny Kotkov
