Author: jan
Date: Mon Feb 24 16:15:39 2020
New Revision: 38254
Log:
remove apache couchdb 2.3.0
Removed:
release/couchdb/source/2.3.0/
Author: jan
Date: Mon Feb 24 16:14:29 2020
New Revision: 38253
Log:
CouchDB 3.0.0 release
Added:
release/couchdb/source/3.0.0/
release/couchdb/source/3.0.0/apache-couchdb-3.0.0.tar.gz (with props)
release/couchdb/source/3.0.0/apache-couchdb-3.0.0.tar.gz.asc
release/couchdb/sourc
> On 24. Feb 2020, at 17:06, Jan Lehnardt wrote:
>
> Dear community,
>
> The vote has now closed.
>
> Thank you to everyone who participated!
>
> The results are:
>
>+1 - 9 votes
>+0 - 0 votes
>-0 - 0 votes
>-1 - 0 votes
>
> The vote is successful.
Reminder about the rele
Dear community,
The vote has now closed.
Thank you to everyone who participated!
The results are:
+1 - 9 votes
+0 - 0 votes
-0 - 0 votes
-1 - 0 votes
The vote is successful.
Thanks,
Jan “I swear I’m not Joan!” Touzet^WLehnardt
—
> On 20. Feb 2020, at 01:16, Joan Touzet wrot
Hey all,
I bit the bullet and spent all day writing all remaining blog posts sans the
actual release announcement. For easier review, I’ve put them all up in the
same google doc (including Mike’s post). Please review thoroughly:
https://docs.google.com/document/d/1mkmK3lgTybqTs2FkmI0ZaMvMqi
Nick,
Thanks for thinking this through, it's certainly subtle and very unclear what
is a "good" solution :(
I have a couple of thoughts, firstly about the guarantees we currently offer
and then wondering whether there is an opportunity to improve our API by
offering a single guarantee across a
