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

Re: Reminder: Branch 1.6 next Wednesday

From: Joe Swatosh <joe.swatosh_at_gmail.com>
Date: Fri, 31 Oct 2008 19:26:58 -0700

On Thu, Oct 30, 2008 at 11:30 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Thu, Oct 30, 2008 at 1:03 PM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
>> There's been a bit of discussion in response to my mail of last week about
>> branching 1.6 on Wednesday (see
>> http://svn.haxx.se/dev/archive-2008-10/0818.shtml). However, I haven't heard
>> any screaming complaints or needs to push the date back, so I'm still planning
>> on branching 1.6 on Nov. 5, 1700 UTC.
>> As I mentioned earlier, if people feel they need another week or so be get stuff
>> in for 1.6, I don't think that's too much of a problem, but please make it known
>> soon!
> There is still several days until Nov. 5, but based on some simple
> testing of trunk yesterday, I do not think the tree conflicts code is
> ready for release. So if we do not think we should plan on fixing
> stuff after we branch, then I do not think we are ready to branch.
> Also, I am not sure what the state of the bindings are at present. It
> sounded in another thread like the Ruby bindings have been broken
> since adding SQLite. JavaHL seems to be OK, but there is still some

I haven't been able to run the Ruby bindings tests since r33730 (Merge
the fs-rep-sharing branch to trunk), but to be fair, not all the
problems are in the bindings. There are some issues with the tests
themselves. I hate committing without have a successful test run, but
I may have to just try for some incremental improvements.

Joe Swatosh
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-01 03:27:26 CET

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.