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

Re: Subversion 1.10.2 up for testing/signing

From: Branko Čibej <brane_at_apache.org>
Date: Mon, 16 Jul 2018 08:11:51 +0200

On 16.07.2018 08:08, Branko Čibej wrote:
> On 16.07.2018 00:46, Johan Corveleyn wrote:
>> On Sat, Jul 14, 2018 at 10:55 PM, Julian Foad <julianfoad_at_apache.org> wrote:
>>> The 1.10.2 release artifacts are now available for testing/signing.
>>> Please get the tarballs from
>>> https://dist.apache.org/repos/dist/dev/subversion
>>> and add your signatures there.
>>> Note that this is code-wise identical to 1.10.1; only the CHANGES file and COMMITTERS file are updated and version numbers changed.
>> I noticed that there is a difference that I didn't expect, in
>> subversion/include/svn_version.h, between the tarball and the 1.10.x
>> branch: on the branch SVN_VER_PATCH is still 0 (while it is 2 in the
>> tarball and in the tag). I don't think it's a big issue (the tarball
>> and tag are correct after all), but it's different from the 1.9
>> situation (in the 1.9.x branch SVN_VER_PATCH is 10 currently (and 9 in
>> 1.9.x@, as expected) and all previous releases.
>> It seems something went wrong with the "Post-release housekeeping"
>> commits on the 1.10.x branch, r1835806 (post 1.10.1) and r1835936
>> (post 1.10.2): they contain an empty diff for svn_version.h ... weird.
>> Fortunately, the values in the tarball and tag are correct, so I don't
>> consider this a big issue right now ... I'm continuing tests ...
> This step is documented in HACKING, 'release.py create-tag' will bump
> the minor version on the release branch.

The last two revisions of release.py affect this area, but I haven't
looked at which one actually broke the version update ...

-- Brane
Received on 2018-07-16 08:12:01 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.