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 <[email protected]> 于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 <[email protected]> 于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 > >
