You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asyncband.apache.org by tison <wa...@gmail.com> on 2026/09/04 07:13:27 UTC

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Merged [1] for solving most of the license issues. Merged [2] to revert the
change for non-ASF release.

[1] https://github.com/apache/asyncband/pull/279
[2] https://github.com/apache/asyncband/pull/280

Before further improvements and finalizing the changeset, I have two early
questions to avoid an at-most-6-days-later objection.

1. Now I merge HISTORY.md into LICENSE. Thus, the LICENSE contains a
section named "DESIGN PROVENANCE WITHOUT INCORPORATED THIRD-PARTY SOURCE".
It tells history but do not convey license terms. Not sure if we should
exclude them from LICENSE or just fair enough to leave them there. An
alternative is moving concrete primitive background to their own modules.

2. Currently, I leave the "Copyright 2025 FastLabs Developers" header for
files derived from fastpool. But since I wrote most of the code, I wonder
whether we can use an ASF license header for these files. I'm fine with
retaining the original license header, but I'd like to test our policies by
setting some examples at the boundary. I believe it is fine, and I know the
only other code contributor of [3] would be glad to transfer his code here.
I'm not sure whether any process is required.

[3] https://github.com/fast/fastpool/pull/17

Keep dev@ informed so that other community member can learn from this
lesson if they have time.

Best,
tison.


tison <wa...@gmail.com> 于2026年9月4日周五 13:52写道:

> > I assume you’re aware that the workflow change only excludes the tag
> v0.7.1, so any other tag still publishes to crates.io.
>
> Yes. I will go through the ASF release process for 0.7.2. Working on
> license provances issues and would prepare a release candidate.
>
> > So deleting DISCLAIMER leaves the podling with no incubation disclaimer
> at all, and we need one in all documentation and releases. A different
> disclaimer message also needs IPMC approval first.
> > I don't think WIP is what you want anyway. It's for ASF releases that
> don't follow all ASF policy, and it needs a list of known issues.
>
> Good to know. I'll revert the DISCLAIMER-WIP to the original DISCLAIMER as
> we are going to make an ASF release.
>
> Best,
> tison.
>
>
> Justin Mclean <ju...@classsoftware.com> 于2026年9月4日周五 13:43写道:
>
>> HI,
>>
>> Thanks for yanking it.
>>
>> On #278, the DISCLAIMER-WIP file doesn't contain the WIP disclaimer. That
>> text is the incubation statement that some releases may not be fully
>> compliant with ASF policy, a list of the issues you're aware of, and the
>> note that downstream users need their own licensing review. What's there is
>> a note that 0.7.1 is not an ASF release, which is a different thing.
>>
>> So deleting DISCLAIMER leaves the podling with no incubation disclaimer
>> at all, and we need one in all documentation and releases. A different
>> disclaimer message also needs IPMC approval first.
>>
>> I don't think WIP is what you want anyway. It's for ASF releases that
>> don't follow all ASF policy, and it needs a list of known issues.
>>
>> I assume you’re aware that the workflow change only excludes the tag
>> v0.7.1, so any other tag still publishes to crates.io.
>>
>> Kind regards,
>>
>> Justin
>
>

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
Hi Sebb,

It's "supply".

This sounds interesting. I saw people say "please drop a comment/review"
and I understand it as "drop down a comment/review". Perhaps like "leave a
comment/review", and finally "give/supply/provide".

Best,
tison.


sebb <se...@gmail.com> 于2026年9月5日周六 00:26写道:

> On Fri, 4 Sept 2026 at 12:48, tison <wa...@gmail.com> wrote:
> >
> > A new PPMC vote thread has started at [1].
> >
> > [1] https://lists.apache.org/thread/xtdrj3q9f23hrok4l0h2l50gfqsf9v7r
> >
> > To IPMC members, feel free to drop early reviews.
>
> The word 'drop' is ambiguous here: does it mean omit, or supply?
>
> > This release candidate is generated by the beta ATR platform [2] and it
> > would form a sequential vote, first PPMC vote and then IPMC vote.
> >
> > [2] https://releases.apache.org/vote/asyncband/0.7.2
> >
> > Best,
> > tison.
> >
> >
> > tison <wa...@gmail.com> 于2026年9月4日周五 16:29写道:
> >
> > > Hi Incubator PMC,
> > >
> > > Here is an overall update on the third-party licensing issues
> identified
> > > during the Apache Asyncband 0.7.0 RC1 vote.
> > >
> > > We cancelled RC1 and completed a file-by-file review of the current
> source
> > > tree and repository history.
> > >
> > > The review identified incorporated source from Tokio, oneshot,
> futures-rs,
> > > Pollster, futures-lite, parking, and Fastpool. We treated code
> > > conservatively as derived, adapted, or ported where applicable.
> > >
> > > For the third-party source that remains, we made the following changes:
> > >
> > > - LICENSE now records the exact local-to-upstream file mappings and
> > > commit-pinned upstream sources.
> > > - Tokio-derived portions retain the Tokio copyright and MIT license.
> > > - Where an upstream project offers an Apache-2.0 or MIT choice,
> Asyncband
> > > uses the Apache-2.0 option.
> > > - Fastpool-derived source and tests retain the original "Copyright 2025
> > > FastLabs Developers" attribution and Apache-2.0 header.
> > > - Each affected source or test file contains an explicit provenance
> note
> > > and a stable upstream source link.
> > > - Files treated as third-party sources retain the applicable upstream
> > > license treatment.
> > > - For files containing substantial Asyncband modifications, the scope
> of
> > > the ASF-authored work and the retained third-party portions is
> documented
> > > explicitly.
> > >
> > > After reviewing the result against the ASF LICENSE and NOTICE
> guidance, we
> > > also removed design and API provenance that does not represent
> incorporated
> > > third-party source from the LICENSE. Such "inspired by" history may
> remain
> > > in source comments, issues, or pull requests where useful, but it does
> not
> > > affect the distribution's licensing.
> > >
> > > Normal Cargo dependencies whose source is not bundled are not listed in
> > > LICENSE. We also checked the incorporated upstream projects for NOTICE
> > > requirements and found no additional notices that need to be
> propagated, so
> > > the project NOTICE remains intentionally brief.
> > >
> > > The remediation is covered by the following pull requests:
> > >
> > > https://github.com/apache/asyncband/pull/275
> > > https://github.com/apache/asyncband/pull/279
> > > https://github.com/apache/asyncband/pull/281
> > > https://github.com/apache/asyncband/pull/283
> > >
> > > The resulting license inventory is available at:
> > >
> > > https://github.com/apache/asyncband/blob/main/LICENSE
> > >
> > > The 0.7.0 ASF release candidate remains canceled, and I yanked the
> > > incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
> > > explicitly marked interim non-ASF release. We will prepare 0.7.2 as a
> fresh
> > > ASF release candidate and restart the PPMC and IPMC votes.
> > >
> > > From the project side, we consider the third-party provenance and
> > > licensing remediation complete, subject to any further PMC feedback.
> > >
> > > Thanks again to Justin and everyone who reviewed RC1 and helped us
> correct
> > > both the release contents and our review process.
> > >
> > > Best,
> > > tison
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by sebb <se...@gmail.com>.
On Fri, 4 Sept 2026 at 12:48, tison <wa...@gmail.com> wrote:
>
> A new PPMC vote thread has started at [1].
>
> [1] https://lists.apache.org/thread/xtdrj3q9f23hrok4l0h2l50gfqsf9v7r
>
> To IPMC members, feel free to drop early reviews.

The word 'drop' is ambiguous here: does it mean omit, or supply?

> This release candidate is generated by the beta ATR platform [2] and it
> would form a sequential vote, first PPMC vote and then IPMC vote.
>
> [2] https://releases.apache.org/vote/asyncband/0.7.2
>
> Best,
> tison.
>
>
> tison <wa...@gmail.com> 于2026年9月4日周五 16:29写道:
>
> > Hi Incubator PMC,
> >
> > Here is an overall update on the third-party licensing issues identified
> > during the Apache Asyncband 0.7.0 RC1 vote.
> >
> > We cancelled RC1 and completed a file-by-file review of the current source
> > tree and repository history.
> >
> > The review identified incorporated source from Tokio, oneshot, futures-rs,
> > Pollster, futures-lite, parking, and Fastpool. We treated code
> > conservatively as derived, adapted, or ported where applicable.
> >
> > For the third-party source that remains, we made the following changes:
> >
> > - LICENSE now records the exact local-to-upstream file mappings and
> > commit-pinned upstream sources.
> > - Tokio-derived portions retain the Tokio copyright and MIT license.
> > - Where an upstream project offers an Apache-2.0 or MIT choice, Asyncband
> > uses the Apache-2.0 option.
> > - Fastpool-derived source and tests retain the original "Copyright 2025
> > FastLabs Developers" attribution and Apache-2.0 header.
> > - Each affected source or test file contains an explicit provenance note
> > and a stable upstream source link.
> > - Files treated as third-party sources retain the applicable upstream
> > license treatment.
> > - For files containing substantial Asyncband modifications, the scope of
> > the ASF-authored work and the retained third-party portions is documented
> > explicitly.
> >
> > After reviewing the result against the ASF LICENSE and NOTICE guidance, we
> > also removed design and API provenance that does not represent incorporated
> > third-party source from the LICENSE. Such "inspired by" history may remain
> > in source comments, issues, or pull requests where useful, but it does not
> > affect the distribution's licensing.
> >
> > Normal Cargo dependencies whose source is not bundled are not listed in
> > LICENSE. We also checked the incorporated upstream projects for NOTICE
> > requirements and found no additional notices that need to be propagated, so
> > the project NOTICE remains intentionally brief.
> >
> > The remediation is covered by the following pull requests:
> >
> > https://github.com/apache/asyncband/pull/275
> > https://github.com/apache/asyncband/pull/279
> > https://github.com/apache/asyncband/pull/281
> > https://github.com/apache/asyncband/pull/283
> >
> > The resulting license inventory is available at:
> >
> > https://github.com/apache/asyncband/blob/main/LICENSE
> >
> > The 0.7.0 ASF release candidate remains canceled, and I yanked the
> > incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
> > explicitly marked interim non-ASF release. We will prepare 0.7.2 as a fresh
> > ASF release candidate and restart the PPMC and IPMC votes.
> >
> > From the project side, we consider the third-party provenance and
> > licensing remediation complete, subject to any further PMC feedback.
> >
> > Thanks again to Justin and everyone who reviewed RC1 and helped us correct
> > both the release contents and our review process.
> >
> > Best,
> > tison
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
A new PPMC vote thread has started at [1].

[1] https://lists.apache.org/thread/xtdrj3q9f23hrok4l0h2l50gfqsf9v7r

To IPMC members, feel free to drop early reviews.

This release candidate is generated by the beta ATR platform [2] and it
would form a sequential vote, first PPMC vote and then IPMC vote.

[2] https://releases.apache.org/vote/asyncband/0.7.2

Best,
tison.


tison <wa...@gmail.com> 于2026年9月4日周五 16:29写道:

> Hi Incubator PMC,
>
> Here is an overall update on the third-party licensing issues identified
> during the Apache Asyncband 0.7.0 RC1 vote.
>
> We cancelled RC1 and completed a file-by-file review of the current source
> tree and repository history.
>
> The review identified incorporated source from Tokio, oneshot, futures-rs,
> Pollster, futures-lite, parking, and Fastpool. We treated code
> conservatively as derived, adapted, or ported where applicable.
>
> For the third-party source that remains, we made the following changes:
>
> - LICENSE now records the exact local-to-upstream file mappings and
> commit-pinned upstream sources.
> - Tokio-derived portions retain the Tokio copyright and MIT license.
> - Where an upstream project offers an Apache-2.0 or MIT choice, Asyncband
> uses the Apache-2.0 option.
> - Fastpool-derived source and tests retain the original "Copyright 2025
> FastLabs Developers" attribution and Apache-2.0 header.
> - Each affected source or test file contains an explicit provenance note
> and a stable upstream source link.
> - Files treated as third-party sources retain the applicable upstream
> license treatment.
> - For files containing substantial Asyncband modifications, the scope of
> the ASF-authored work and the retained third-party portions is documented
> explicitly.
>
> After reviewing the result against the ASF LICENSE and NOTICE guidance, we
> also removed design and API provenance that does not represent incorporated
> third-party source from the LICENSE. Such "inspired by" history may remain
> in source comments, issues, or pull requests where useful, but it does not
> affect the distribution's licensing.
>
> Normal Cargo dependencies whose source is not bundled are not listed in
> LICENSE. We also checked the incorporated upstream projects for NOTICE
> requirements and found no additional notices that need to be propagated, so
> the project NOTICE remains intentionally brief.
>
> The remediation is covered by the following pull requests:
>
> https://github.com/apache/asyncband/pull/275
> https://github.com/apache/asyncband/pull/279
> https://github.com/apache/asyncband/pull/281
> https://github.com/apache/asyncband/pull/283
>
> The resulting license inventory is available at:
>
> https://github.com/apache/asyncband/blob/main/LICENSE
>
> The 0.7.0 ASF release candidate remains canceled, and I yanked the
> incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
> explicitly marked interim non-ASF release. We will prepare 0.7.2 as a fresh
> ASF release candidate and restart the PPMC and IPMC votes.
>
> From the project side, we consider the third-party provenance and
> licensing remediation complete, subject to any further PMC feedback.
>
> Thanks again to Justin and everyone who reviewed RC1 and helped us correct
> both the release contents and our review process.
>
> Best,
> tison
>

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
A new PPMC vote thread has started at [1].

[1] https://lists.apache.org/thread/xtdrj3q9f23hrok4l0h2l50gfqsf9v7r

To IPMC members, feel free to drop early reviews.

This release candidate is generated by the beta ATR platform [2] and it
would form a sequential vote, first PPMC vote and then IPMC vote.

[2] https://releases.apache.org/vote/asyncband/0.7.2

Best,
tison.


tison <wa...@gmail.com> 于2026年9月4日周五 16:29写道:

> Hi Incubator PMC,
>
> Here is an overall update on the third-party licensing issues identified
> during the Apache Asyncband 0.7.0 RC1 vote.
>
> We cancelled RC1 and completed a file-by-file review of the current source
> tree and repository history.
>
> The review identified incorporated source from Tokio, oneshot, futures-rs,
> Pollster, futures-lite, parking, and Fastpool. We treated code
> conservatively as derived, adapted, or ported where applicable.
>
> For the third-party source that remains, we made the following changes:
>
> - LICENSE now records the exact local-to-upstream file mappings and
> commit-pinned upstream sources.
> - Tokio-derived portions retain the Tokio copyright and MIT license.
> - Where an upstream project offers an Apache-2.0 or MIT choice, Asyncband
> uses the Apache-2.0 option.
> - Fastpool-derived source and tests retain the original "Copyright 2025
> FastLabs Developers" attribution and Apache-2.0 header.
> - Each affected source or test file contains an explicit provenance note
> and a stable upstream source link.
> - Files treated as third-party sources retain the applicable upstream
> license treatment.
> - For files containing substantial Asyncband modifications, the scope of
> the ASF-authored work and the retained third-party portions is documented
> explicitly.
>
> After reviewing the result against the ASF LICENSE and NOTICE guidance, we
> also removed design and API provenance that does not represent incorporated
> third-party source from the LICENSE. Such "inspired by" history may remain
> in source comments, issues, or pull requests where useful, but it does not
> affect the distribution's licensing.
>
> Normal Cargo dependencies whose source is not bundled are not listed in
> LICENSE. We also checked the incorporated upstream projects for NOTICE
> requirements and found no additional notices that need to be propagated, so
> the project NOTICE remains intentionally brief.
>
> The remediation is covered by the following pull requests:
>
> https://github.com/apache/asyncband/pull/275
> https://github.com/apache/asyncband/pull/279
> https://github.com/apache/asyncband/pull/281
> https://github.com/apache/asyncband/pull/283
>
> The resulting license inventory is available at:
>
> https://github.com/apache/asyncband/blob/main/LICENSE
>
> The 0.7.0 ASF release candidate remains canceled, and I yanked the
> incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
> explicitly marked interim non-ASF release. We will prepare 0.7.2 as a fresh
> ASF release candidate and restart the PPMC and IPMC votes.
>
> From the project side, we consider the third-party provenance and
> licensing remediation complete, subject to any further PMC feedback.
>
> Thanks again to Justin and everyone who reviewed RC1 and helped us correct
> both the release contents and our review process.
>
> Best,
> tison
>

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
Hi Incubator PMC,

Here is an overall update on the third-party licensing issues identified
during the Apache Asyncband 0.7.0 RC1 vote.

We cancelled RC1 and completed a file-by-file review of the current source
tree and repository history.

The review identified incorporated source from Tokio, oneshot, futures-rs,
Pollster, futures-lite, parking, and Fastpool. We treated code
conservatively as derived, adapted, or ported where applicable.

For the third-party source that remains, we made the following changes:

- LICENSE now records the exact local-to-upstream file mappings and
commit-pinned upstream sources.
- Tokio-derived portions retain the Tokio copyright and MIT license.
- Where an upstream project offers an Apache-2.0 or MIT choice, Asyncband
uses the Apache-2.0 option.
- Fastpool-derived source and tests retain the original "Copyright 2025
FastLabs Developers" attribution and Apache-2.0 header.
- Each affected source or test file contains an explicit provenance note
and a stable upstream source link.
- Files treated as third-party sources retain the applicable upstream
license treatment.
- For files containing substantial Asyncband modifications, the scope of
the ASF-authored work and the retained third-party portions is documented
explicitly.

After reviewing the result against the ASF LICENSE and NOTICE guidance, we
also removed design and API provenance that does not represent incorporated
third-party source from the LICENSE. Such "inspired by" history may remain
in source comments, issues, or pull requests where useful, but it does not
affect the distribution's licensing.

Normal Cargo dependencies whose source is not bundled are not listed in
LICENSE. We also checked the incorporated upstream projects for NOTICE
requirements and found no additional notices that need to be propagated, so
the project NOTICE remains intentionally brief.

The remediation is covered by the following pull requests:

https://github.com/apache/asyncband/pull/275
https://github.com/apache/asyncband/pull/279
https://github.com/apache/asyncband/pull/281
https://github.com/apache/asyncband/pull/283

The resulting license inventory is available at:

https://github.com/apache/asyncband/blob/main/LICENSE

The 0.7.0 ASF release candidate remains canceled, and I yanked the
incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
explicitly marked interim non-ASF release. We will prepare 0.7.2 as a fresh
ASF release candidate and restart the PPMC and IPMC votes.

From the project side, we consider the third-party provenance and licensing
remediation complete, subject to any further PMC feedback.

Thanks again to Justin and everyone who reviewed RC1 and helped us correct
both the release contents and our review process.

Best,
tison

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
Hi Incubator PMC,

Here is an overall update on the third-party licensing issues identified
during the Apache Asyncband 0.7.0 RC1 vote.

We cancelled RC1 and completed a file-by-file review of the current source
tree and repository history.

The review identified incorporated source from Tokio, oneshot, futures-rs,
Pollster, futures-lite, parking, and Fastpool. We treated code
conservatively as derived, adapted, or ported where applicable.

For the third-party source that remains, we made the following changes:

- LICENSE now records the exact local-to-upstream file mappings and
commit-pinned upstream sources.
- Tokio-derived portions retain the Tokio copyright and MIT license.
- Where an upstream project offers an Apache-2.0 or MIT choice, Asyncband
uses the Apache-2.0 option.
- Fastpool-derived source and tests retain the original "Copyright 2025
FastLabs Developers" attribution and Apache-2.0 header.
- Each affected source or test file contains an explicit provenance note
and a stable upstream source link.
- Files treated as third-party sources retain the applicable upstream
license treatment.
- For files containing substantial Asyncband modifications, the scope of
the ASF-authored work and the retained third-party portions is documented
explicitly.

After reviewing the result against the ASF LICENSE and NOTICE guidance, we
also removed design and API provenance that does not represent incorporated
third-party source from the LICENSE. Such "inspired by" history may remain
in source comments, issues, or pull requests where useful, but it does not
affect the distribution's licensing.

Normal Cargo dependencies whose source is not bundled are not listed in
LICENSE. We also checked the incorporated upstream projects for NOTICE
requirements and found no additional notices that need to be propagated, so
the project NOTICE remains intentionally brief.

The remediation is covered by the following pull requests:

https://github.com/apache/asyncband/pull/275
https://github.com/apache/asyncband/pull/279
https://github.com/apache/asyncband/pull/281
https://github.com/apache/asyncband/pull/283

The resulting license inventory is available at:

https://github.com/apache/asyncband/blob/main/LICENSE

The 0.7.0 ASF release candidate remains canceled, and I yanked the
incorrectly published 0.7.0 crate. Version 0.7.1 was published as an
explicitly marked interim non-ASF release. We will prepare 0.7.2 as a fresh
ASF release candidate and restart the PPMC and IPMC votes.

From the project side, we consider the third-party provenance and licensing
remediation complete, subject to any further PMC feedback.

Thanks again to Justin and everyone who reviewed RC1 and helped us correct
both the release contents and our review process.

Best,
tison

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by tison <wa...@gmail.com>.
> I'd remove the design provenance from LICENSE. LICENSE is for license
terms and for third-party code you've actually incorporated. Follow the
how-to for what goes in LICENSE [1]

Thanks for your advice. This sounds reasonable to me.

> If you do want ASF headers on those files, the process is IP clearance.
But fastpool is already Apache-2.0, so nothing is wrong as it stands, and I
don't see what you gain.

Yes it is. Let me retain the original headers then.

Best,
tison.


<ju...@classsoftware.com> 于2026年9月4日周五 16:00写道:

> Hi,
>
> I'd remove the design provenance from LICENSE. LICENSE is for license
> terms and for third-party code you've actually incorporated. Follow the
> how-to for what goes in LICENSE [1]
>
> Keep the fastpool attribution. "I wrote most of it" isn't the test. The
> copyright line says FastLabs Developers, so it's held by the people who
> wrote it, and you're one of them, not all of them. You can contribute your
> own work under your ICLA, but you can't grant someone else's.
>
> If you do want ASF headers on those files, the process is IP clearance.
> But fastpool is already Apache-2.0, so nothing is wrong as it stands, and I
> don't see what you gain.
>
> I'd also not test policy boundaries in a release that's already had two
> false starts. Get the ASF release done with the safe option, and if you
> want the boundary settled, raise it separately on legal-discuss.
>
> Kind regards,
>
> Justin
>
> 1. https://infra.apache.org/licensing-howto.html

Re: [CANCEL][VOTE] Release Apache Asyncband (Incubating) 0.7.0 RC1

Posted by ju...@classsoftware.com.
Hi,

I'd remove the design provenance from LICENSE. LICENSE is for license terms and for third-party code you've actually incorporated. Follow the how-to for what goes in LICENSE [1]

Keep the fastpool attribution. "I wrote most of it" isn't the test. The copyright line says FastLabs Developers, so it's held by the people who wrote it, and you're one of them, not all of them. You can contribute your own work under your ICLA, but you can't grant someone else's.

If you do want ASF headers on those files, the process is IP clearance. But fastpool is already Apache-2.0, so nothing is wrong as it stands, and I don't see what you gain.

I'd also not test policy boundaries in a release that's already had two false starts. Get the ASF release done with the safe option, and if you want the boundary settled, raise it separately on legal-discuss.

Kind regards,

Justin

1. https://infra.apache.org/licensing-howto.html