couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell Branca <chewbra...@gmail.com>
Subject Re: [VOTE] Apache CouchDB maintenance releases, first round for 1.0.4, 1.1.2, 1.2.1
Date Tue, 08 Jan 2013 21:10:07 GMT
I retested 1.0.4 on Debian Squeeze with Erlang R14B04 and switched over to
SpiderMonkey 1.7.0, and the view_sandboxing test completed successfully, in
addition to make check and the rest of the futon tests passing.

I noticed Dave successfully tested 1.0.4 on a nearly identical setup, so
possibly something odd with my setup.

Given the tests are passing now, I'm +1 on 1.0.4.

I'll test the other two releases tonight.


-Russell


On Tue, Jan 8, 2013 at 11:40 AM, Dave Cottlehuber <dch@jsonified.com> wrote:

> On 29 December 2012 21:12, Dave Cottlehuber <dch@apache.org> wrote:
> > maintenance releases, to start your New Year with a bang.
> >
> > We encourage the whole community to download and test these release
> > artifacts so that any critical issues can be resolved before the releases
> > are made. Everyone is free to vote on this release, so get stuck in!
> >
> > We are voting on the following release artifacts, by different release
> > managers to spread the load.
> >
> > Robert Newson:
> >     http://people.apache.org/~rnewson/dist/1.0.4
> >
> > Dave Cottlehuber:
> >     http://people.apache.org/~dch/dist/1.1.2
> >     http://people.apache.org/~dch/dist/1.2.1
> >
> > PGP Keys:
> >     https://people.apache.org/~dch/dist/KEYS
> >
> > These artifacts have been built from the following git commits:
> >
> > 1.0.4: 514b7ef95cf67a06f094d56b6ab86b4a770292bd
> > 1.1.2: 306a6eb4405de878313b46ef026a6089503b693a
> > 1.2.1: 5ebfa8e4bce7322ae0d7b7d95f269425cdb9a46c
> >
> > Please follow the test procedure before voting:
> >
> > http://wiki.apache.org/couchdb/Test_procedure
> >
> > Note the following restrictions for both 1.0.4 and 1.1.2:
> >
> > Erlang/OTP R14B* or lower
> > Spidermonkey 1.8.0rc1 or lower
> >
> > Thank you.
> >
> > Happy voting,
> > Dave & Bob.
>
> +3, "all for one and one for all", caveat for 1.1.2 on Windows.
>
> Browsers used for testing:
>
> OSX Mountain Lion (aka cuddly cat)
> Mozilla Nightly 20.0a1 (2013-01-07)
> Chrome Canary: Version 26.0.1377.0 canary
>
> 1.2.1 ===== +1 ======
> sig, sha, md5 OK
> autotools diff OK
> make check OK
> Debian:
>     Squeeze amd64
>     Erlangs: both R14b04 & R15b01, x64
>     SpiderMonkey: 1.8.0rc1 (JavaScript-C 1.8.0 pre-release 1 2007-10-03)
>     tests:
>         mozilla: all passed
>         canary: all passed except attachments as usual (ref rnewson's note)
> Windows:
>     Windows 7 N Enterprise x64
>     Erlangs: R14B04 x86
>     Spidermonkey: 1.8.5-1.0.0
>     tests:
>         mozilla: all passed
>         canary: all passed except attachments as usual
>
> 1.1.2 ===== +1 ======
> sig, sha, md5 OK
> autotools diff OK
> make check OK
> Debian:
>     Squeeze amd64
>     Erlangs: R14b04, x64
>     SpiderMonkey: 1.8.0rc1 (JavaScript-C 1.8.0 pre-release 1 2007-10-03)
>     tests:
>         mozilla: all passed
>         canary:  all passed
> Windows:
>     Windows 7 N Enterprise x64
>     Erlangs: R14B04 x86
>     Spidermonkey: 1.8.5-1.0.0
>     tests:
>         mozilla: all passed except attachments & attachment_names
>         canary:  all passed except attachments & attachment_names
>             Assertion failed: expected '"\"qUUYqS41RhwF0TrCsTAxFg==\""',
>                 got '"\"jeLnIuUvK7d+6gya044lVA==\""'
>     This issue was introduced as part of COUCHDB-1337, and workaround
>     committed in #8d83b3
> https://issues.apache.org/jira/browse/COUCHDB-1379
>     "Compressed attachments do not produce a consistent digest across
> platforms,
>     due to differing compression algorithms between Mac/Linux and Windows."
>
>     The attachment tests used content-type:text/plain which is set in
>     default.ini as a compressible type. Using octet-stream bypasses
>     couchdb compressing the attachment.
>
>     I'm +1 as this issue is a cosmetic one, with a fix already in place
>     in 1.2.0 and higher. The actual etag is correctly calculated, just
>     the assumption in the test that the compression algorithm across
>     platforms is not correct. I don't forsee a situation that this will
>     impact users.
>
> 1.0.4 ===== +1 ======
> sig, sha, md5 OK
> autotools diff OK
> make check OK
> Debian:
>     Squeeze amd64
>     Erlang: R14b04, x64
>     SpiderMonkey: 1.8.0rc1 (JavaScript-C 1.8.0 pre-release 1 2007-10-03)
>     tests:
>         mozilla: all passed
>         canary: all passed
>
> A+
> Dave
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message