I think faulty test case should block the release, if I am to have any
future sanity preparing releases. I don't want to delay and longer, so
if you guys are absolutely sure this is a test error and not code
error, then I propose that the test be commented out. Our tests form a
contract between us, internally, and our users. If that contract has a
bug, it should be removed or fixed - or it simply dilutes the
importance of contract. If some one comments out the test, and we
agree it is not indicative of an important bug, I can call the vote
within hours.
On 20 Mar 2010, at 18:19, Benoit Chesneau <bchesn...@gmail.com> wrote:
On Sat, Mar 20, 2010 at 7:17 PM, Jan Lehnardt <j...@apache.org> wrote:
On 20 Mar 2010, at 10:26, Noah Slater wrote:
Jan, should this block the release? From what I can tell, it should.
I don't think a faulty test case should block the release.
Cheers
Jan
are we sure it's a faulty test? For what it worth i reproduce it in
python in couchdbkit unittests.
- benoit
