Re: API review for 1.11; do we need to mark new APIs as experimental?

2018-09-12 Thread Branko Čibej
On 12.09.2018 22:16, Daniel Shahaf wrote: > Julian Foad wrote on Wed, 12 Sep 2018 20:21 +0100: >> The following public APIs are new or revved since 1.10: >> >> svn_client_layout_func_t >> svn_client_layout_list >> - New for 'viewspec' output; marked 'experimental'. >>> svn_client_diff7 >> svn_cli

Re: API review for 1.11; do we need to mark new APIs as experimental?

2018-09-12 Thread Daniel Shahaf
Julian Foad wrote on Wed, 12 Sep 2018 20:21 +0100: > The following public APIs are new or revved since 1.10: > > svn_client_layout_func_t > svn_client_layout_list > - New for 'viewspec' output; marked 'experimental'. > > svn_client_diff7 > svn_client_diff_peg7 > - Adds a 'pretty_print_mergeinf

Re: 1.11 release preparation [was: Feature freeze for 1.11]

2018-09-12 Thread Daniel Shahaf
Julian Foad wrote on Wed, 12 Sep 2018 20:39 +0100: > I will plan to release 1.11 on 2018-10-17 which is a Wednesday 5 weeks > from today. I have to enter a planned release date in the CHANGES file, I'm not sure you do, not yet. The tarball you'll soon be rolling will be called 1.11.0-rc1, not 1

1.11 release preparation [was: Feature freeze for 1.11]

2018-09-12 Thread Julian Foad
Julian Foad wrote: > James McCoy wrote: > > I could still use some help getting the Java 10 support finalized [...] > > For my planning of the 1.11 branch, could you please tell/remind me [...] That was answered on IRC: it does not block the 1.11 branching or release. I will plan to release 1.11

API review for 1.11; do we need to mark new APIs as experimental?

2018-09-12 Thread Julian Foad
The following public APIs are new or revved since 1.10: svn_client_layout_func_t svn_client_layout_list - New for 'viewspec' output; marked 'experimental'. svn_client_diff7 svn_client_diff_peg7 - Adds a 'pretty_print_mergeinfo' option. svn_client_revert4 svn_wc_revert6 - Adds an 'added_kee

Re: svn commit: r1840708 - /subversion/trunk/CHANGES

2018-09-12 Thread Julian Foad
Daniel Shahaf wrote: > I think the target audience of the "Developer-visible changes" is API > consumers, meaning that these three changes should be removed, since > they're only of interest to maintainers (i.e., us). Ack. r1840730. -- - Julian

Re: svn commit: r1840708 - /subversion/trunk/CHANGES

2018-09-12 Thread Daniel Shahaf
julianf...@apache.org wrote on Wed, 12 Sep 2018 15:48 +: > + Developer-visible changes: > + - General: > +* new tool to automate steps in branching a minor release (r1817962...) > +* Add write-changelog command to release.py (r1818988) > +* Split long help strings into paragraphs t

Translation of Subversion

2018-09-12 Thread Julian Foad
Hello Translators! You are receiving this mail because you are listed as a translator in the Subversion COMMITTERS file[1]. I'm writing on behalf of the Subversion developers to let you know that we're getting close to wrapping up development for Subversion 1.11, and we would like to encourage you