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

Re: Hide experimental APIs to unblock 1.11 release

From: Stefan Kueng <tortoisesvn_at_gmail.com>
Date: Thu, 20 Sep 2018 18:39:22 +0200

On 9/20/2018 5:17 PM, Julian Foad wrote:
> A fresh perspective on the experimental-APIs issue just came to me: this should not hold up the 1.11 release. We were falling into the old trap of thrashing about debating how to do it, assuming we needed some solution for 1.11, but we don't. One of the rules of time-based releases: something that need not block it should not block it.
> We should just pull the experimental APIs from the public API space (moving them into the private API space) and get on with the release.

But if they're in the private space, other clients can not use them.
Sure, I could add some workaround in the TSVN build to pull in the
private headers, but then that would mean I wouldn't get any compiler
error if I actually use a private and not just an experimental API.

Why not just leave it like it is for now - the docs clearly mark the
APIs as experimental, and IMHO that's good enough (at least for now).


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
Received on 2018-09-20 18:39:35 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.