[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Finalizing the 1.14.0 release notes

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Wed, 27 May 2020 10:35:02 -0400

To finalize the release notes for 1.14.0, I think there are just these
three changes to make:

(1) Document the test failures that occur on Windows with links to the
    revisions (and/or patches) that fix them. Say that "these issues
    are expected to be fixed in the next point release" or something
    to that effect.

(2) We haven't come to a formal decision on which minor lines of Py3
    we will "promise" to support through the life of 1.14, so I
    propose to not make any promises and instead just remove the #TODO

        TODO: Describe which minor releases of Python 3.x we plan to
        support through the four-year LTS period of Subversion 1.14.
        Per recent discussions on the dev@ mailing list, that might be
        some form of "rolling" support: In each 1.14.x patch release,
        we would make an effort to support the oldest through newest
        minor lines of Python 3.x that Python upstream supports at the
        time of our release. However, we could drop support for the
        oldest one if we have a compelling reason to do so.

    Unless the other devs feel that we should state something here,
    but if so, then what?

(3) Under "Python 3 support is incomplete" we are linking to a wiki
    page "Subversion's Python 3 Support Status" at [1]. That page is
    being used by the developers to track the status of each Python
    script; it more closely represents trunk than any release. Should
    the current state of that page be copied (perhaps formatted
    differently) into the release notes to preserve the record of
    what's actually in this release?

Am I missing anything?


[1] https://cwiki.apache.org/confluence/display/SVN/Subversion%27s+Python+3+Support+Status
Received on 2020-05-27 16:35:25 CEST

This is an archived mail posted to the Subversion Dev mailing list.