Re: Time for 7.0.39

2013-03-22 Thread Mark Thomas
On 21/03/2013 22:34, Mark Thomas wrote: > On 20/03/2013 20:55, Mark Thomas wrote: >> I plan to get the most recent FileUpload changes (if any), run the unit >> tests, run the TCKs and then tag 7.0.39 so that should happen some time >> early tomorrow if all goes well. > > Second attempt. > > Unit

Re: Time for 7.0.39

2013-03-21 Thread Mark Thomas
On 20/03/2013 20:55, Mark Thomas wrote: > I plan to get the most recent FileUpload changes (if any), run the unit > tests, run the TCKs and then tag 7.0.39 so that should happen some time > early tomorrow if all goes well. Second attempt. Unit tests for 7.0.x/trunk both passed. Running the TCKs n

Re: Time for 7.0.39

2013-03-20 Thread Mark Thomas
On 20/03/2013 20:58, Nick Williams wrote: > > On Mar 20, 2013, at 3:55 PM, Mark Thomas wrote: > >> I plan to get the most recent FileUpload changes (if any), run the unit >> tests, run the TCKs and then tag 7.0.39 so that should happen some time >> early tomorrow if all goes well. >> >> Mark > >

Re: Time for 7.0.39

2013-03-20 Thread Mark Thomas
On 20/03/2013 21:31, Konstantin Kolinko wrote: > 2013/3/21 Mark Thomas : >> I plan to get the most recent FileUpload changes (if any), run the unit >> tests, run the TCKs and then tag 7.0.39 so that should happen some time >> early tomorrow if all goes well. > > 1. There are some jdbc-pool bugs th

Re: Time for 7.0.39

2013-03-20 Thread Konstantin Kolinko
2013/3/21 Mark Thomas : > I plan to get the most recent FileUpload changes (if any), run the unit > tests, run the TCKs and then tag 7.0.39 so that should happen some time > early tomorrow if all goes well. 1. There are some jdbc-pool bugs that are worth looking at https://issues.apache.org/bugzil

Re: Time for 7.0.39

2013-03-20 Thread Nick Williams
On Mar 20, 2013, at 3:55 PM, Mark Thomas wrote: > I plan to get the most recent FileUpload changes (if any), run the unit > tests, run the TCKs and then tag 7.0.39 so that should happen some time > early tomorrow if all goes well. > > Mark In 54734 I propose a patch that needs to also be back-p