couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wendall Cada <wenda...@83864.com>
Subject Re: Status of 1.2.x and 1.3.x branches
Date Tue, 19 Mar 2013 17:15:51 GMT
On 03/19/2013 10:09 AM, Noah Slater wrote:
> Thanks for the info guys.
>
> Wendall, were you able to ascertain whether the failures were in CouchDB or
> the tests?
The only test that I was suspicious of has a ticket already. 
https://issues.apache.org/jira/browse/COUCHDB-1716

I'm trying to free up some time to deal with the tests in the next 
couple of days. I don't think this will be a blocker for the releases 
though.

Wendall
> For the record, ./configure --disable-tests is a workaround if you need it.
> ;)
>
>
> On 18 March 2013 22:48, Jan Lehnardt <jan@apache.org> wrote:
>
>> Great summary Wendall!
>>
>> On Mar 18, 2013, at 23:41 , Wendall Cada <wendallc@83864.com> wrote:
>>
>>> Note: I am not a committer for the project, I've just been following
>> this current release cycle closely.
>>> For 1.2.x
>>> It appears as though all blockers have been resolved, allowing for a
>> 1.2.2 rc.
>>
>> +1
>>
>>> For 1.3.x
>>> Only issues remaining in the blockers list (
>> http://s.apache.org/couchdb_130_blockers) are
>> https://issues.apache.org/jira/browse/COUCHDB-1696 (Support Erlang/OTP
>> R16B)
>>> The only other issues for 1.3.x, not on the list are the intermittent
>> test failures.
>>
>> I fixed one of them at
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commitdiff;h=f36232c8(COUCHDB-1711)
>>
>> and filed another one just now:
>>
>>    https://issues.apache.org/jira/browse/COUCHDB-1716
>>
>>
>>> I think the only questions here remaining are:
>>>
>>> 1. Can 1.3.0 ship without COUCHDB-1696?
>> Injecting the new Mochiweb is a non-trivial patch that I’d say we are not
>> comfortable
>> adding to a release branch with barely any testing. As much as it sucks
>> I’d say we
>> should ship 1.3.0 without R16B support with big warnings in the release
>> notes.
>>
>> We should also merge the new Mochiweb asap and get our testing on and
>> release a 1.3.1
>> and 1.2.3 as soon as we are comfortable with it.
>>
>>
>>> 2. Can 1.3.0 ship with known test issues?
>> I don’t think we have much of a choice here, as the test suite remains
>> brittle in some
>> configurations. We are still on the way to make it better, but this isn’t
>> done yet
>> and I don’t think this will be doable in a short amount of time.
>>
>> We might want to opt for disabling or working around the tests that we
>> know to fail.
>>
>>
>> Again, thanks for compiling this!
>>
>> Jan
>> --
>>
>>
>>
>>> Wendall
>>>
>>> On 03/17/2013 09:58 AM, Jan Lehnardt wrote:
>>>> On Mar 16, 2013, at 21:46 , Noah Slater <nslater@apache.org> wrote:
>>>>
>>>>> Hey devs,
>>>>>
>>>>> When will 1.2.x
>>>> 1.2.x is ready for 1.2.2 now.
>>>>
>>>>> and 1.3.x be ready for me to cut release candidates?
>>>> There are a few issues up on http://s.apache.org/couchdb_130_blockersthat
are being worked through.
>>>>
>>>> Cheers
>>>> Jan
>>
>


Mime
View raw message