Hi Xuanwo, Thank you for the thorough review and the binding -1. We confirmed each item on the current RC.
1) LICENSE "(i)" -> "(properties)" Confirmed. Diff against LICENSE-2.0.txt shows this is the only change in the terms; it is in all four LICENSE files. We had only checked that a LICENSE file existed. Apache License 2.0 is fixed text, so we will restore the official "(i)" wording. 2) Bootstrap v3.0.3 header replaced by an ASF header Confirmed. Compared with upstream Bootstrap 3.0.3: the Twitter / Apache-2.0 banner is gone. Our header checker requires an ASF header and did not ignore this vendored file. We will restore the upstream banner, exclude it from licenserc, and list it in LICENSE. We saw the same pattern on font-awesome.css. We plan to treat it the same way — is that OK? 3) Binary tar root has no LICENSE / NOTICE Confirmed. Unpacked root only has DISCLAIMER; LICENSE/NOTICE are under seata-server/ and seata-namingserver/. The assembly never copied them to the tarball root. We understand each distribution needs LICENSE and NOTICE at package root. We will add combined files there and keep the per-component copies. Does that layout look right to you? 4) BOM lists missing seata-threadpool-loom; omits json-common-jackson3 Confirmed. Both modules are JDK-gated: json-common-jackson3 requires JDK 17+, while seata-threadpool-loom requires JDK 21+. Loom is listed in the BOM but missing from staging; jackson3 is neither in the BOM nor staging. We will publish both with the required JDKs, keep loom in the BOM, add jackson3, and document their JDK requirements. A BOM coordinate should correspond to an artifact that is actually published, and we will align the BOM with the artifacts in staging under this publication plan. I have also sent a [CANCEL][VOTE] message for this thread. We will rebuild, re-sign, and restart the vote after fixing these issues. Thank you again. Best regards, Minghua
