You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Joan Touzet <wo...@apache.org> on 2017/07/16 21:44:09 UTC
2.1.0 milestone progress report
Hi everyone,
Here are the results of the progress towards the 2.1.0 milestone
as captured in our issue tracking system (GitHub Issues).
https://github.com/apache/couchdb/milestone/2
At present, we have just 10 of 55 tickets against the 2.1.0 milestone
that remain open. Broken down:
* 1 minor feature ticket remains:
* #593, improving the _cluster_setup endpoint/Fauxton wizard for
single-node automatic setup
* 7 test-case related failures remain:
* 3 are related to the JavaScript test suite
* 4 are related to the Erlang EUnit test suite
* 6 of these appear to be related to flaky test cases
* 1 is a single occurrence of a replication failure from June 3
and has not recurred since then, but deserves more investigation
because of the failure mode
* 1 is to update the documentation for the 2.1 "What's New" page
* 1 is build pipeline related, and strictly speaking does not block
a 2.1 release. It addresses automation of package building,
publication of "convenience builds" for those binaries, and
migration of the Docker image into the apache/couchdb namespace
In my opinion, the priority order of these tasks should be:
* #593 (Complete update of the setup wizard for standalone single nodes)
* #574 (One-off attachment-related replication failure in couch_att)
* Cleanup on remaining 6 test case failure tickets
* #683 ("What's New in 2.1")
* Package building & publication work (some work depends on Apache Infra)
There has been significant progress in the past week, and I'd like to
personally thank everyone involved. I am feeling more confident that
we are ready to release.
-Joan