Hi IPMC and Community,

Thank you all for the careful review and valuable feedback on RC6.

As a PPMC member, I'd like to share an update on our progress in
addressing the concerns raised:

1. Website exclusion: The entire website/ directory is now completely
excluded from the canonical source release package via .gitattributes
export-ignore and assembly exclusions[1].

2. SVG licensing & headers: Since website/ is no longer bundled in the
source release tarball, assets like github.svg are not added to the
root LICENSE. In addition, the incorrectly injected ASF headers on
these SVGs in the git repository have been cleaned up[2].

3. unDraw SVGs: All Category X unDraw illustrations have been
completely removed and replaced with compliant assets in the
repository [3].

4. IPMC feedback addressed: The other points raised by Justin have
been completed—cleaning up the stale WIP description in pom.xml,
ensuring DISCLAIMER is included in the JAR's META-INF, and documenting
pre-donation releases.

5. Alibaba copyright headers:
In our previous discussion [4], the community initially adopted the
"Pekko Route"—retaining the original Alibaba attribution in derived
source files alongside the standard ASF header, in addition to the
attribution in NOTICE. However, Justin's point is also very
well-taken: with the Software Grant in place and attribution already
preserved in NOTICE, having widespread third-party copyright headers
in individual source files is unnecessary and non-standard. To
establish the definitive and compliant path forward without ambiguity,
we will bring this directly to the ASF Legal Affairs committee right
after this release for official guidance.

Given these fixes, I suggest that our Release Manager cancel the
current RC6 vote and prepare the RC7 vote within the next 72 hours.

Please let us know if there are any further thoughts or suggestions.

[1] https://github.com/apache/fesod/issues/1111
[2] https://github.com/apache/fesod/issues/1113
[3] https://github.com/apache/fesod/issues/1112
[4] https://lists.apache.org/thread/5mzx51ndl8by1tzstpr5l7k3b118wp60

Best regards,

Shuxin Pan

Apache Fesod (Incubating) PPMC

On Tue, Sep 15, 2026 at 9:18 PM ian <[email protected]> wrote:
>
> Hello everyone,
>
> This is a call for vote to release Apache Fesod(incubating)
> 2.1.0-incubating.
>
> The Apache Fesod (incubating)   community has voted and approved the
> release of Apache Fesod (incubating) 2.1.0-incubating.
> We now kindly request the IPMC members review and vote for this release.
>
> The vote thread:
> https://lists.apache.org/thread/34yff7xqvkbdgrp7fqy34t6vcozt00ww
>
> Vote Result:
> https://lists.apache.org/thread/kzvrjgc3mkx4ho4llpdhnr5y9519fbc5
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/fesod/2.1.0-incubating-rc6
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapachefesod-1056
>
> Git tag for the release:
> https://github.com/apache/fesod/releases/tag/2.1.0-incubating-rc6
>
> Hash for the release tag: 8f1e1e1272a61b8b0892dfebe270258626ca5d00
>
> Release Notes:
> https://github.com/apache/fesod/releases/tag/2.1.0-incubating-rc6
>
> The artifacts have been signed with Key [
> CCCFA0EAA4BFB4A441D4D770FDD68C1D3497B880 ],
> corresponding to [ [email protected] ] which can be found in the keys
> file: https://downloads.apache.org/incubator/fesod/KEYS
>
> Build Environment: JDK 8+, Apache Maven 3.6.0+. ./mvnw clean package
> -DskipTests
>
> The vote will be open for at least 72 hours.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> To learn more about Apache Fesod (Incubating) , please see
> https://fesod.apache.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to