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 2020/04/21 15:59:07 UTC

[DISCUSS] CouchDB 3.0.1 and 3.1.0 release plans

Hello devs,

We need to get some important patches out to the community for 3.x. We 
also have two new features, JWT and SpiderMonkey 68 support, that need 
to land.


I propose the following:

* Release 3.0.1 with all of the bugfixes to date. Robert Newson has done
   the bulk of the work here, keeping our 3.0.x and 3.x branches up to
   date with the changes on master as of a couple of weeks ago. We
   probably need one more pass before release.

* Release 3.1.0 with JWT and SM 68 support. The former is a lovely
   feature, and the latter is mandatory for us to release Ubuntu 20.04
   "Focal Fossa" packages. (20.04 releases April 23rd, Thursday. At this
   point I don't think we'll release in time for it, but we'll be close,
   anyway.)

Any objections?


The following are blockers for these releases:

* https://github.com/apache/couchdb-documentation/pull/524 - Docs for
   JWT.

* https://github.com/apache/couchdb/pull/2788 - SM68 support, one
   failing test case. Paul is on this one.

* https://github.com/apache/couchdb/pull/2798 and any add'l fixes for
   #2797 - setup wizard bug

* 2x Release notes PRs (TBD)


If anyone has anything else that needs to land on the 3.x or 3.0.x 
branches, please make a PR now and reply to this list so we know to 
review and merge it.

-Joan "last call" Touzet

Re: [DISCUSS] CouchDB 3.0.1 and 3.1.0 release plans

Posted by Joan Touzet <wo...@apache.org>.
On 2020-05-17 3:06, Justin Mclean wrote:
> Hi,
> 
>> Justin, which line of that file?
> 
> This one:
> "Copyright 2020 The Apache Foundation”
> 
> It should be:
>   Copyright [yyyy] [name of copyright owner]
> 
> As it’s an instruction on how to apply the license to your own work.

PR up, needs +1 before merging from someone:

https://github.com/apache/couchdb/pull/2891

>> Will someone on dev@ volunteer to resolve this? Thanks.
> 
> I’m happy to help if you need it just ask.

As the saying goes.... "Pull Requests welcome" :D Thanks for the offer.

-Joan "off to bed" Touzet

> Thanks,
> Justin

Re: [DISCUSS] CouchDB 3.0.1 and 3.1.0 release plans

Posted by Justin Mclean <jm...@apache.org>.
Hi,

> Justin, which line of that file?

This one:
"Copyright 2020 The Apache Foundation”

It should be:
 Copyright [yyyy] [name of copyright owner]

As it’s an instruction on how to apply the license to your own work.

> Will someone on dev@ volunteer to resolve this? Thanks.

I’m happy to help if you need it just ask.

Thanks,
Justin

Re: [DISCUSS] CouchDB 3.0.1 and 3.1.0 release plans

Posted by Joan Touzet <wo...@apache.org>.
On 2020-05-17 2:43, Justin Mclean wrote:
> Hi there,
> I took a look at your recent release and noticed a couple of issues. Be aware I'm not part of your project, and I'm missing a large part of your history, so these things may have been discussed before and are that way for good reasons.
> - Your license file has an incorrect copyright line in the license appendix.

Justin, which line of that file?

> - Your notice file lists the copyright of 3rd party dependencies. This is not how a notice file works. You need to include relevant parts from ALv2 bundled code notice files and relocated copyrights. Relocated copyright only occurs when a 3rd party header is replaced during a software grant. [1]

Will someone on dev@ volunteer to resolve this? Thanks.

> - Your release contains code that is under the Erlang Public License. This is category B and as such can't normally be included in a source release in the form it's in. [2] I couldn't find any discussion on this. How was it decided that this code was OK to include?

Looks like this was missed with the 2.0 import. Paul did the work in 
2016 prior to the 2.0 release:

https://github.com/apache/couchdb-couch-log/commit/b6b766ddfbff8db789723689419ee6f634e752b8#diff-e7183b47c7155debfec662d667b6fcd4

https://github.com/cloudant/couchdb/commit/094ceae9fd81f1d71647728d4a2e583423618914

https://issues.apache.org/jira/browse/COUCHDB-3067

Paul, how do you want to proceed? Looks like it's just 2 files that we 
can replace quickly and spin new releases, but we'll have to go back and 
do a 2.3.2 as well, and expunge 2.3.1.

-Joan


> Thanks,
> Justin
> 
> P.S I'm not subscribed to this list so please CC me on any replies.
> 
> 1. https://www.apache.org/dev/licensing-howto.html
> 2. https://www.apache.org/legal/resolved.html#category-b
> 

Re: [DISCUSS] CouchDB 3.0.1 and 3.1.0 release plans

Posted by Justin Mclean <jm...@apache.org>.
Hi there,
I took a look at your recent release and noticed a couple of issues. Be aware I'm not part of your project, and I'm missing a large part of your history, so these things may have been discussed before and are that way for good reasons.
- Your license file has an incorrect copyright line in the license appendix.
- Your notice file lists the copyright of 3rd party dependencies. This is not how a notice file works. You need to include relevant parts from ALv2 bundled code notice files and relocated copyrights. Relocated copyright only occurs when a 3rd party header is replaced during a software grant. [1]
- Your release contains code that is under the Erlang Public License. This is category B and as such can't normally be included in a source release in the form it's in. [2] I couldn't find any discussion on this. How was it decided that this code was OK to include?
Thanks,
Justin

P.S I'm not subscribed to this list so please CC me on any replies.

1. https://www.apache.org/dev/licensing-howto.html
2. https://www.apache.org/legal/resolved.html#category-b

FINAL CALL Re: [DISCUSS] CouchDB 3.0.1 and 3.1.0 release

Posted by Joan Touzet <wo...@apache.org>.
Hello again everyone,

This is the Final Call for 3.0.1/3.1.0 changes.

Release notes for 3.0.1 are up: 
http://docs.couchdb.org/en/latest/whatsnew/3.0.html#version-3-0-1

I'll get to the rel notes for 3.1.0 tomorrow, but it's basically 3.0.1 + 
JWT + SM68 support.

We are currently waiting only on Fauxton improvements. Once those land, 
and rebar.config.script is updated with it + docs, I can cut the first 
RCs. That should happen no later than Wednesday.

I look forward to everyone's help testing the RCs!

-Joan "no time like the present" Touzet


On 2020-04-21 11:59 a.m., Joan Touzet wrote:
> Hello devs,
> 
> We need to get some important patches out to the community for 3.x. We 
> also have two new features, JWT and SpiderMonkey 68 support, that need 
> to land.
> 
> 
> I propose the following:
> 
> * Release 3.0.1 with all of the bugfixes to date. Robert Newson has done
>    the bulk of the work here, keeping our 3.0.x and 3.x branches up to
>    date with the changes on master as of a couple of weeks ago. We
>    probably need one more pass before release.
> 
> * Release 3.1.0 with JWT and SM 68 support. The former is a lovely
>    feature, and the latter is mandatory for us to release Ubuntu 20.04
>    "Focal Fossa" packages. (20.04 releases April 23rd, Thursday. At this
>    point I don't think we'll release in time for it, but we'll be close,
>    anyway.)
> 
> Any objections?
> 
> 
> The following are blockers for these releases:
> 
> * https://github.com/apache/couchdb-documentation/pull/524 - Docs for
>    JWT.
> 
> * https://github.com/apache/couchdb/pull/2788 - SM68 support, one
>    failing test case. Paul is on this one.
> 
> * https://github.com/apache/couchdb/pull/2798 and any add'l fixes for
>    #2797 - setup wizard bug
> 
> * 2x Release notes PRs (TBD)
> 
> 
> If anyone has anything else that needs to land on the 3.x or 3.0.x 
> branches, please make a PR now and reply to this list so we know to 
> review and merge it.
> 
> -Joan "last call" Touzet