Re: 'svn list --search' feature complete? (was: re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-08-21 Thread Julian Foad
Johan Corveleyn wrote: > On Sun, Jan 29, 2017 at 10:35 AM, Stefan Fuhrmann wrote: >> Originally, I wanted to complete the get_list API before the alpha >> release but I can't make any commitments. So, it is probably better >> to roll the alpha with whatever is on /trunk at

'svn list --search' feature complete? (was: re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-08-18 Thread Johan Corveleyn
On Sun, Jan 29, 2017 at 10:35 AM, Stefan Fuhrmann wrote: > On 24.01.2017 12:20, Stefan Sperling wrote: ... >> I would like to get an 1.10.0 alpha1 released in February. Unless I hear >> objections I will start rolling this alpha release from trunk and call a >> vote on it

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-29 Thread Stefan Fuhrmann
On 24.01.2017 12:20, Stefan Sperling wrote: Hi, Another update on the new conflict resolver: We have 36 conflict resolver tests, all of which PASS. I have updated the wiki page about conflict tests accordingly: https://wiki.apache.org/subversion/TreeConflictTests The 36 tests we have still do

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-25 Thread Daniel Shahaf
Stefan Sperling wrote on Wed, Jan 25, 2017 at 11:37:30 +0100: > On Tue, Jan 24, 2017 at 07:06:29PM +, Daniel Shahaf wrote: > > Stefan Sperling wrote on Tue, Jan 24, 2017 at 19:06:13 +0100: > > That's just a synchronization problem and is easily solved. I'm more > > concerned that we'd need to

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-25 Thread Stefan Hett
On 1/25/2017 11:37 AM, Stefan Sperling wrote: On Tue, Jan 24, 2017 at 07:06:29PM +, Daniel Shahaf wrote: Stefan Sperling wrote on Tue, Jan 24, 2017 at 19:06:13 +0100: On Tue, Jan 24, 2017 at 05:52:39PM +, Daniel Shahaf wrote: [...] If we do this, it would be good to know upfront

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-25 Thread Stefan Sperling
On Tue, Jan 24, 2017 at 07:06:29PM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, Jan 24, 2017 at 19:06:13 +0100: > > On Tue, Jan 24, 2017 at 05:52:39PM +, Daniel Shahaf wrote: > > > I wonder if we should delay the release announcement until we can link > > > to a bunch of

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-25 Thread Stefan Sperling
On Tue, Jan 24, 2017 at 11:41:47PM +0100, Johan Corveleyn wrote: > On Tue, Jan 24, 2017 at 12:20 PM, Stefan Sperling wrote: > > Hi, > > > > Another update on the new conflict resolver: > > > > We have 36 conflict resolver tests, all of which PASS. > > I have updated the wiki page

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Johan Corveleyn
On Tue, Jan 24, 2017 at 12:20 PM, Stefan Sperling wrote: > Hi, > > Another update on the new conflict resolver: > > We have 36 conflict resolver tests, all of which PASS. > I have updated the wiki page about conflict tests accordingly: >

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, Jan 24, 2017 at 19:06:13 +0100: > On Tue, Jan 24, 2017 at 05:52:39PM +, Daniel Shahaf wrote: > > I wonder if we should delay the release announcement until we can link > > to a bunch of .deb/.rpm/GUIs/* from it. This way, once we do announce@, > > we can hope for

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Stefan Sperling
On Tue, Jan 24, 2017 at 05:52:39PM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, Jan 24, 2017 at 18:45:37 +0100: > > On Tue, Jan 24, 2017 at 05:08:51PM +, Daniel Shahaf wrote: > > > - Asking downstreams (distros) to make alpha1 packages easily available > > > to opting-in users

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, Jan 24, 2017 at 18:45:37 +0100: > On Tue, Jan 24, 2017 at 05:08:51PM +, Daniel Shahaf wrote: > > - Asking downstreams (distros) to make alpha1 packages easily available to > > opting-in users > > Yes we can do that. But this is often ineffective because distros

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Stefan Sperling
On Tue, Jan 24, 2017 at 05:08:51PM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, Jan 24, 2017 at 12:20:39 +0100: > > I would like to get an 1.10.0 alpha1 released in February. Unless I hear > > objections I will start rolling this alpha release from trunk and call a > > vote on it

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, Jan 24, 2017 at 12:20:39 +0100: > I would like to get an 1.10.0 alpha1 released in February. Unless I hear > objections I will start rolling this alpha release from trunk and call a > vote on it soon. That all sounds good. However, last time we did that we had

conflict resolver status update (roll 1.10.0 alpha 1?)

2017-01-24 Thread Stefan Sperling
Hi, Another update on the new conflict resolver: We have 36 conflict resolver tests, all of which PASS. I have updated the wiki page about conflict tests accordingly: https://wiki.apache.org/subversion/TreeConflictTests The 36 tests we have still do not cover much of the overall problem space.