You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Denitsa Burroughs <de...@gmail.com> on 2020/01/08 21:55:38 UTC
CouchDB 3.0 Update - Jan 8
Hi all,
Thanks to everyone who contributed with closing the remaining 3.0 roadmap
items/epics. We are getting very close to RC! There are a couple of
outstanding lower level issues that also need to be addressed and any help
here would be greatly appreciated. I am adding owners to each issue based
on the comments in the ticket but please feel free to let me know if that's
incorrect.
Here's a link to the 3.0.0 Milestone
<https://github.com/apache/couchdb/milestone/5>. There are currently 6
items on the list:
#2404 3.0 build is broken on Microsoft Windows
<https://github.com/apache/couchdb/issues/2404> Joan has a fix
#2391 update rebar.config with latest module tags
<https://github.com/apache/couchdb/issues/2391> - Need a
decision/consensus on the approach. Adam/Jan?
#1783 fix empty queries <https://github.com/apache/couchdb/pull/1783> -
Tony?
#2393 fix(#2143): allow env var overrides for js query server config
<https://github.com/apache/couchdb/pull/2393>- blocked by #2404. Joa
#2218 Deprecation list for 3.0 (release notes compilation)
<https://github.com/apache/couchdb/issues/2218> - Doc ticket
#1927 build: stop propagating RC tags into erlang apps
<https://github.com/apache/couchdb/pull/1927> - Dave/Joan?
Any other issues that need to be tagged for 3.0?
Thanks,
Deni
Re: [PLEASE READ] CouchDB 3.0 Update - Jan 30
Posted by Joan Touzet <wo...@apache.org>.
OK Adam, just remember that CI needs to be rejiggered to work for this
scenario, as `master` is protected. A minimum is a functional
Jenkinsfile.pr that runs FDB during `make check`, I presume. Ideally,
we'd get Jenkinsfile.full working, too, but that's probably a larger
task. (I need a break ;) )
-Joan
On 2020-01-30 21:23, Adam Kocoloski wrote:
> Hi Joan,
>
> I think moving the FDB work to master and having a 3.x branch is a good idea. Cheers,
>
> Adam
>
>> On Jan 30, 2020, at 5:58 PM, Joan Touzet <wo...@apache.org> wrote:
>>
>> Hi everyone,
>>
>> We are finally past our blockers for 3.0.0. The beam hang in Erlang 21 and 22 seems to be worked around by not raising the priority of the couch_server process to high. An upstream bug has been filed with Erlang to resolve this; until that get patched and merged, and we blacklist the bad Erlang releases, we're disabling the priority raise.
>>
>> There are only minor documentation, packaging and build changes left to make. I predict RC1 will be cut next week.
>>
>> I intend to fork a 3.0.x branch off of master very soon - possibly *tomorrow*. If anyone has any reason why this shouldn't happen, please speak now.
>>
>> This means if you want anything to end up in CouchDB 3.0.0, this is the final call to clean up and merge your PRs ASAP.
>>
>> If you have patches that affect CouchDB, this means that patches may have to be PR'ed *twice*, once for the 3.0.x branch and once for master.
>>
>> Remember, once FDB work hits master, we'll be in a situation where patches may be landing on multiple branches (if they affect both FDB and non-FDB CouchDB) or may only end up on a 3.* branch.
>>
>> Because of this, do we want to fork now as "3.x", and then fork 3.0.x off of that? Basically, we'd treat 3.x as our new 'master' for merging anything non-FDB, and open up master for FDB releases. If FDB landing on master isn't a priority, we can continue with our traditional forking of 3.1.x, 3.2.x, etc. off of master until FDB is ready to land there.
>>
>> -Joan
>
Re: [PLEASE READ] CouchDB 3.0 Update - Jan 30
Posted by Adam Kocoloski <ko...@apache.org>.
Hi Joan,
I think moving the FDB work to master and having a 3.x branch is a good idea. Cheers,
Adam
> On Jan 30, 2020, at 5:58 PM, Joan Touzet <wo...@apache.org> wrote:
>
> Hi everyone,
>
> We are finally past our blockers for 3.0.0. The beam hang in Erlang 21 and 22 seems to be worked around by not raising the priority of the couch_server process to high. An upstream bug has been filed with Erlang to resolve this; until that get patched and merged, and we blacklist the bad Erlang releases, we're disabling the priority raise.
>
> There are only minor documentation, packaging and build changes left to make. I predict RC1 will be cut next week.
>
> I intend to fork a 3.0.x branch off of master very soon - possibly *tomorrow*. If anyone has any reason why this shouldn't happen, please speak now.
>
> This means if you want anything to end up in CouchDB 3.0.0, this is the final call to clean up and merge your PRs ASAP.
>
> If you have patches that affect CouchDB, this means that patches may have to be PR'ed *twice*, once for the 3.0.x branch and once for master.
>
> Remember, once FDB work hits master, we'll be in a situation where patches may be landing on multiple branches (if they affect both FDB and non-FDB CouchDB) or may only end up on a 3.* branch.
>
> Because of this, do we want to fork now as "3.x", and then fork 3.0.x off of that? Basically, we'd treat 3.x as our new 'master' for merging anything non-FDB, and open up master for FDB releases. If FDB landing on master isn't a priority, we can continue with our traditional forking of 3.1.x, 3.2.x, etc. off of master until FDB is ready to land there.
>
> -Joan
Re: [PLEASE READ] CouchDB 3.0 Update - Jan 30
Posted by Jan Lehnardt <ja...@apache.org>.
Heya Joan,
Barring any substantial extra work to keep CI going on the 3.x branch as it would on master, I think branching off 3.x now, cutting 3.0.0 from that and continuing with FDB wok on master is a good way forward.
Best
Jan
—
> On 30. Jan 2020, at 23:58, Joan Touzet <wo...@apache.org> wrote:
>
> Hi everyone,
>
> We are finally past our blockers for 3.0.0. The beam hang in Erlang 21 and 22 seems to be worked around by not raising the priority of the couch_server process to high. An upstream bug has been filed with Erlang to resolve this; until that get patched and merged, and we blacklist the bad Erlang releases, we're disabling the priority raise.
>
> There are only minor documentation, packaging and build changes left to make. I predict RC1 will be cut next week.
>
> I intend to fork a 3.0.x branch off of master very soon - possibly *tomorrow*. If anyone has any reason why this shouldn't happen, please speak now.
>
> This means if you want anything to end up in CouchDB 3.0.0, this is the final call to clean up and merge your PRs ASAP.
>
> If you have patches that affect CouchDB, this means that patches may have to be PR'ed *twice*, once for the 3.0.x branch and once for master.
>
> Remember, once FDB work hits master, we'll be in a situation where patches may be landing on multiple branches (if they affect both FDB and non-FDB CouchDB) or may only end up on a 3.* branch.
>
> Because of this, do we want to fork now as "3.x", and then fork 3.0.x off of that? Basically, we'd treat 3.x as our new 'master' for merging anything non-FDB, and open up master for FDB releases. If FDB landing on master isn't a priority, we can continue with our traditional forking of 3.1.x, 3.2.x, etc. off of master until FDB is ready to land there.
>
> -Joan
[PLEASE READ] CouchDB 3.0 Update - Jan 30
Posted by Joan Touzet <wo...@apache.org>.
Hi everyone,
We are finally past our blockers for 3.0.0. The beam hang in Erlang 21
and 22 seems to be worked around by not raising the priority of the
couch_server process to high. An upstream bug has been filed with Erlang
to resolve this; until that get patched and merged, and we blacklist the
bad Erlang releases, we're disabling the priority raise.
There are only minor documentation, packaging and build changes left to
make. I predict RC1 will be cut next week.
I intend to fork a 3.0.x branch off of master very soon - possibly
*tomorrow*. If anyone has any reason why this shouldn't happen, please
speak now.
This means if you want anything to end up in CouchDB 3.0.0, this is the
final call to clean up and merge your PRs ASAP.
If you have patches that affect CouchDB, this means that patches may
have to be PR'ed *twice*, once for the 3.0.x branch and once for master.
Remember, once FDB work hits master, we'll be in a situation where
patches may be landing on multiple branches (if they affect both FDB and
non-FDB CouchDB) or may only end up on a 3.* branch.
Because of this, do we want to fork now as "3.x", and then fork 3.0.x
off of that? Basically, we'd treat 3.x as our new 'master' for merging
anything non-FDB, and open up master for FDB releases. If FDB landing on
master isn't a priority, we can continue with our traditional forking of
3.1.x, 3.2.x, etc. off of master until FDB is ready to land there.
-Joan
Re: CouchDB 3.0 Update - Jan 23
Posted by Joan Touzet <wo...@apache.org>.
Hello,
Well, we're basically where we were last week.
We have 2 blocker bugs (segfaults in couchjs SM60 on x86_64 is reopened,
and the BEAM VM hangs).
We have 2 new core dumps from couchjs SM60 x86_64 that are in the
reopened ticket.
Recent critical patches to Erlang 20/21/22 did *not* fix the VM hangs,
but it seems that our soak tests on Erlang 20 don't crash this way.
Blacklisting 21/22 is an option, but not one we should rush into.
Any help tracking down these bugs very much appreciated.
-Joan
On 2020-01-15 22:15, Peng Hui Jiang wrote:
> Hi Joan, Deni and others,
>
> While waiting for provision and getting ready for soak test against SM
> 60 using ppc64le environment,
> I would like to pick up below one to across the finish line.
>
> ======
> * #1783 needs attention; Tony Sun was the original developer here and
> we're hoping someone can carry his work across the finish line
>
> ======
>
>
> Best regards,
> Peng Hui
>
> Inactive hide details for Joan Touzet ---2020/01/16 04:45:50 AM---Hi
> Deni and others, Since you last sent this, a few things haJoan Touzet
> ---2020/01/16 04:45:50 AM---Hi Deni and others, Since you last sent
> this, a few things have happened:
>
> From: Joan Touzet <wo...@apache.org>
> To: dev@couchdb.apache.org
> Date: 2020/01/16 04:45 AM
> Subject: [EXTERNAL] Re: CouchDB 3.0 Update - Jan 15
>
> ------------------------------------------------------------------------
>
>
>
> Hi Deni and others,
>
> Since you last sent this, a few things have happened:
>
> * We found ongoing, persistent crashes in couchjs after upgrading to
> SpiderMonkey 60. The bulk of these appear to have been removed by
> disabling the Ion JIT. The rest appear relegated to a specific
> architecture (arm64), where we need to enforce running against
> 1.8.5 for now. Paul is working this one through #2449.
>
> * In CI runs we're seeing hung Erlang beam.smp processes, consuming
> 100% CPU. We have a traceback from Nick's laptop as well. It's not
> clear this is entirely related to couchjs crashing, especially because
> it's happening on FreeBSD when Jenkins attempts to kill off CouchDB
> forcibly during a test run. This is being tracked in #2437.
>
> There are a couple of new tickets:
>
> * #1783 needs attention; Tony Sun was the original developer here and
> we're hoping someone can carry his work across the finish line
>
> * #2435/#2218 covers documentation work that must be done before 3.0 can
> release. There's quite a lot of this, unfortunately, and a separate
> milestone has been created in the documentation repository to track
> it: https://github.com/apache/couchdb-documentation/milestone/1
> I'm about 75% of the way done with the Release Notes PR, but it is
> still draft status and not yet ready to be reviewed.
>
> * #1927 is a nice-to-have that will make our RC process cleaner, but
> isn't mandatory. Am hoping Dave can help with this, but if not I can
> give some attention once the documentation work is in hand.
>
> * #2457 is a chore to just add a few missed default config params to the
> default.ini file we ship.
>
> * (pending) Our Docker and packaging repos need to be updated with the
> outcome of the SpiderMonkey changes that have been made. The goal is
> to use SM60 if possible, reverting to 1.8.5 when it is not available
> upstream or if there are platform-specific bugs (as with arm64).
>
> On 2020-01-08 16:55, Denitsa Burroughs wrote:
> > Hi all,
> >
> > Thanks to everyone who contributed with closing the remaining 3.0 roadmap
> > items/epics. We are getting very close to RC! There are a couple of
> > outstanding lower level issues that also need to be addressed and any
> help
> > here would be greatly appreciated. I am adding owners to each issue based
> > on the comments in the ticket but please feel free to let me know if
> that's
> > incorrect.
> >
> > Here's a link to the 3.0.0 Milestone
> > <https://github.com/apache/couchdb/milestone/5 >. There are currently 6
> > items on the list:
> > #2404 3.0 build is broken on Microsoft Windows
> > <https://github.com/apache/couchdb/issues/2404 > Joan has a fix
> > #2391 update rebar.config with latest module tags
> > <https://github.com/apache/couchdb/issues/2391 > - Need a
> > decision/consensus on the approach. Adam/Jan?
> > #1783 fix empty queries <https://github.com/apache/couchdb/pull/1783 > -
> > Tony?
> > #2393 fix(#2143): allow env var overrides for js query server config
> > <https://github.com/apache/couchdb/pull/2393 >- blocked by #2404. Joa
> > #2218 Deprecation list for 3.0 (release notes compilation)
> > <https://github.com/apache/couchdb/issues/2218 > - Doc ticket
> > #1927 build: stop propagating RC tags into erlang apps
> > <https://github.com/apache/couchdb/pull/1927 > - Dave/Joan?
> >
> > Any other issues that need to be tagged for 3.0?
> >
> > Thanks,
> >
> > Deni
> >
>
>
>
>
RE: CouchDB 3.0 Update - Jan 15
Posted by Peng Hui Jiang <ji...@cn.ibm.com>.
Hi Joan, Deni and others,
While waiting for provision and getting ready for soak test against SM 60
using ppc64le environment,
I would like to pick up below one to across the finish line.
======
* #1783 needs attention; Tony Sun was the original developer here and
we're hoping someone can carry his work across the finish line
======
Best regards,
Peng Hui
From: Joan Touzet <wo...@apache.org>
To: dev@couchdb.apache.org
Date: 2020/01/16 04:45 AM
Subject: [EXTERNAL] Re: CouchDB 3.0 Update - Jan 15
Hi Deni and others,
Since you last sent this, a few things have happened:
* We found ongoing, persistent crashes in couchjs after upgrading to
SpiderMonkey 60. The bulk of these appear to have been removed by
disabling the Ion JIT. The rest appear relegated to a specific
architecture (arm64), where we need to enforce running against
1.8.5 for now. Paul is working this one through #2449.
* In CI runs we're seeing hung Erlang beam.smp processes, consuming
100% CPU. We have a traceback from Nick's laptop as well. It's not
clear this is entirely related to couchjs crashing, especially because
it's happening on FreeBSD when Jenkins attempts to kill off CouchDB
forcibly during a test run. This is being tracked in #2437.
There are a couple of new tickets:
* #1783 needs attention; Tony Sun was the original developer here and
we're hoping someone can carry his work across the finish line
* #2435/#2218 covers documentation work that must be done before 3.0 can
release. There's quite a lot of this, unfortunately, and a separate
milestone has been created in the documentation repository to track
it:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb-2Ddocumentation_milestone_1&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=3wFZBNiTEQftiGFJt2AjFS2EWuelZsiagaVN0Wlqie0&e=
I'm about 75% of the way done with the Release Notes PR, but it is
still draft status and not yet ready to be reviewed.
* #1927 is a nice-to-have that will make our RC process cleaner, but
isn't mandatory. Am hoping Dave can help with this, but if not I can
give some attention once the documentation work is in hand.
* #2457 is a chore to just add a few missed default config params to the
default.ini file we ship.
* (pending) Our Docker and packaging repos need to be updated with the
outcome of the SpiderMonkey changes that have been made. The goal is
to use SM60 if possible, reverting to 1.8.5 when it is not available
upstream or if there are platform-specific bugs (as with arm64).
On 2020-01-08 16:55, Denitsa Burroughs wrote:
> Hi all,
>
> Thanks to everyone who contributed with closing the remaining 3.0 roadmap
> items/epics. We are getting very close to RC! There are a couple of
> outstanding lower level issues that also need to be addressed and any
help
> here would be greatly appreciated. I am adding owners to each issue based
> on the comments in the ticket but please feel free to let me know if
that's
> incorrect.
>
> Here's a link to the 3.0.0 Milestone
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_milestone_5&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=a4XvUwW4qdOV_5mgk8Oe-Ra7cES1pQ20iUz_RjeQDUg&e=
>. There are currently 6
> items on the list:
> #2404 3.0 build is broken on Microsoft Windows
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_issues_2404&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=IqviXa-nypBueWTvqr5LahsUObxazEZLLNOLvlMGN1U&e=
> Joan has a fix
> #2391 update rebar.config with latest module tags
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_issues_2391&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=R2BcclAQR2l62aBOAX_b0h4ZbRs8jGAXKghkUz3q6vc&e=
> - Need a
> decision/consensus on the approach. Adam/Jan?
> #1783 fix empty queries <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_pull_1783&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=EmUSbLKtHrsej7OX-W-Swz9U1TlRQ8SH0NMJPgk6rAw&e=
> -
> Tony?
> #2393 fix(#2143): allow env var overrides for js query server config
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_pull_2393&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=wZt_Y-Pv2_Md6yITDsQw3cP3XsxZJAXieitVrhX05Sc&e=
>- blocked by #2404. Joa
> #2218 Deprecation list for 3.0 (release notes compilation)
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_issues_2218&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=9SPlBn8YMGrgSv7HW0Cpq8UEmOn5q-z92OUjsLf4yLw&e=
> - Doc ticket
> #1927 build: stop propagating RC tags into erlang apps
> <
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_couchdb_pull_1927&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=PKZ65oA9tV05sXjYYyZUJf_d-ASaaLXiLw-gQdWPDsQ&m=bOjhux-5fL3vcK82IqEu9OACs5WHJZ4UD7mYed1HK88&s=ayicblf79Xtq9DBzOVf4IkAos1iSX719ee31SMzLVSo&e=
> - Dave/Joan?
>
> Any other issues that need to be tagged for 3.0?
>
> Thanks,
>
> Deni
>
Re: CouchDB 3.0 Update - Jan 15
Posted by Joan Touzet <wo...@apache.org>.
Hi Deni and others,
Since you last sent this, a few things have happened:
* We found ongoing, persistent crashes in couchjs after upgrading to
SpiderMonkey 60. The bulk of these appear to have been removed by
disabling the Ion JIT. The rest appear relegated to a specific
architecture (arm64), where we need to enforce running against
1.8.5 for now. Paul is working this one through #2449.
* In CI runs we're seeing hung Erlang beam.smp processes, consuming
100% CPU. We have a traceback from Nick's laptop as well. It's not
clear this is entirely related to couchjs crashing, especially because
it's happening on FreeBSD when Jenkins attempts to kill off CouchDB
forcibly during a test run. This is being tracked in #2437.
There are a couple of new tickets:
* #1783 needs attention; Tony Sun was the original developer here and
we're hoping someone can carry his work across the finish line
* #2435/#2218 covers documentation work that must be done before 3.0 can
release. There's quite a lot of this, unfortunately, and a separate
milestone has been created in the documentation repository to track
it: https://github.com/apache/couchdb-documentation/milestone/1
I'm about 75% of the way done with the Release Notes PR, but it is
still draft status and not yet ready to be reviewed.
* #1927 is a nice-to-have that will make our RC process cleaner, but
isn't mandatory. Am hoping Dave can help with this, but if not I can
give some attention once the documentation work is in hand.
* #2457 is a chore to just add a few missed default config params to the
default.ini file we ship.
* (pending) Our Docker and packaging repos need to be updated with the
outcome of the SpiderMonkey changes that have been made. The goal is
to use SM60 if possible, reverting to 1.8.5 when it is not available
upstream or if there are platform-specific bugs (as with arm64).
On 2020-01-08 16:55, Denitsa Burroughs wrote:
> Hi all,
>
> Thanks to everyone who contributed with closing the remaining 3.0 roadmap
> items/epics. We are getting very close to RC! There are a couple of
> outstanding lower level issues that also need to be addressed and any help
> here would be greatly appreciated. I am adding owners to each issue based
> on the comments in the ticket but please feel free to let me know if that's
> incorrect.
>
> Here's a link to the 3.0.0 Milestone
> <https://github.com/apache/couchdb/milestone/5>. There are currently 6
> items on the list:
> #2404 3.0 build is broken on Microsoft Windows
> <https://github.com/apache/couchdb/issues/2404> Joan has a fix
> #2391 update rebar.config with latest module tags
> <https://github.com/apache/couchdb/issues/2391> - Need a
> decision/consensus on the approach. Adam/Jan?
> #1783 fix empty queries <https://github.com/apache/couchdb/pull/1783> -
> Tony?
> #2393 fix(#2143): allow env var overrides for js query server config
> <https://github.com/apache/couchdb/pull/2393>- blocked by #2404. Joa
> #2218 Deprecation list for 3.0 (release notes compilation)
> <https://github.com/apache/couchdb/issues/2218> - Doc ticket
> #1927 build: stop propagating RC tags into erlang apps
> <https://github.com/apache/couchdb/pull/1927> - Dave/Joan?
>
> Any other issues that need to be tagged for 3.0?
>
> Thanks,
>
> Deni
>
Re: CouchDB 3.0 Update - Jan 8
Posted by Joan Touzet <wo...@apache.org>.
Hi Deni,
On 2020-01-08 4:55 p.m., Denitsa Burroughs wrote:
> Hi all,
>
> Thanks to everyone who contributed with closing the remaining 3.0 roadmap
> items/epics. We are getting very close to RC! There are a couple of
> outstanding lower level issues that also need to be addressed and any help
> here would be greatly appreciated. I am adding owners to each issue based
> on the comments in the ticket but please feel free to let me know if that's
> incorrect.
>
> Here's a link to the 3.0.0 Milestone
> <https://github.com/apache/couchdb/milestone/5>. There are currently 6
> items on the list:
> #2404 3.0 build is broken on Microsoft Windows
> <https://github.com/apache/couchdb/issues/2404> Joan has a fix
Fixed and checked in today.
> #2391 update rebar.config with latest module tags
> <https://github.com/apache/couchdb/issues/2391> - Need a
> decision/consensus on the approach. Adam/Jan?
The very last step of this will be to bump the documentation repo, once
the release notes have been written. Because of this, #2391 will be the
last ticket to get closed before the RC is cut.
> #1783 fix empty queries <https://github.com/apache/couchdb/pull/1783> -
> Tony?
> #2393 fix(#2143): allow env var overrides for js query server config
> <https://github.com/apache/couchdb/pull/2393>- blocked by #2404. Joa
This got fixed and merged today too.
> #2218 Deprecation list for 3.0 (release notes compilation)
> <https://github.com/apache/couchdb/issues/2218> - Doc ticket
Tracking this separate from #2391 is good since deprecation
documentation deserves more eyes than the usual laundry list in release
notes
> #1927 build: stop propagating RC tags into erlang apps
> <https://github.com/apache/couchdb/pull/1927> - Dave/Joan?
Pinged Dave on this, but will have a look this week.
>
> Any other issues that need to be tagged for 3.0?
>
> Thanks,
>
> Deni
>