Hi all,

We are withdrawing release candidate #4 of Apache Fesod (Incubating)
version 2.1.0-incubating. The vote on this candidate is hereby closed
as canceled.

Reason
------
During review, a release-blocking concern was raised (tison, -1 binding
vote; PJ Fanning) about publishing two source-release artifacts in
dist/dev:

  apache-fesod-2.1.0-incubating-src.tar.gz
  fesod-parent-2.1.0-incubating-source-release.zip

without explaining why both are needed. The podling's source release
should present a single canonical source archive as the object of the
vote. The Maven-assembly `source-release.zip` is a deploy helper for the
Maven ecosystem, not a second, independent source release, and should
not be co-listed as a community source artifact in dist/dev.

As stated in the Apache Incubator Release Votes guidelines, a release
vote applies to a single, immutable set of artifacts. Because the
presentation of this candidate must be corrected, this vote is hereby
withdrawn and any votes already cast cannot be considered on the
corrected contents.

Follow-up cleanup already completed
-----------------------------------
- dist/dev hygiene: removed obsolete RC1/RC2/RC3 directories (r87353);
  removed the KEYS file from the dev channel (r87349).
dist/dev/incubator/fesod
  now contains only the current candidate.
- Corrected the 404 verification-guide link in the VOTE email and the
  test count discrepancy (the automation now derives both from the
  actual artifacts).

Next steps
----------
A corrected release candidate RC5 will be prepared with:

- a single canonical source archive (`git archive` tar.gz of the tagged
  commit) as the object of the vote;
- the Maven `source-release.zip` kept on the Nexus staging side only and
  clearly labeled as a Maven deploy helper;
- a fresh VOTE email auto-generated from the actual artifacts, with a
  valid verification-guide link and CI-derived test count.

We apologize for the churn and thank you for the careful review.

Best regards,
Zhe Zhang
Release Manager, Apache Fesod (Incubating)

Reply via email to