后端【免费下载链接】fesodFast. Easy. Done. Processing spreadsheets without worrying about large files causing OOM.项目地址https://gitcode.com/gh_mirrors/fast/fesod点击查看免费下载Apache Fesod孵化中是一个面向海量表格文件处理的高性能 Java 库核心实现位于 fesod-sheet 模块。作为 Apache 孵化器项目其每个版本的发布都必须遵循 ASF 规范化的 Release 流程。本文以仓库中 website/community/release/release-version.md 为骨架完整讲解从 Release Manager 准备PGP 密钥、KEYS 文件、Maven 配置、RC 产物构建与签名、社区投票、Incubator 投票到最终发布公告的全过程并辅以仓库源码与配置作为佐证。读完本文你将能够独立完成 Apache Fesod 一次完整版本的发布与验证。1. 发布前准备Preparation1.1 阅读官方发布指南在动手之前Release Manager 应首先通读 ASF 官方发布规则理解「发布即合规」的核心要求。文档中列出的关键参考包括Apache Release Guide发布物如何发布到 downloads.apache.orgApache Release Policy版本号、投票、归档等整体政策Apache Incubator Release孵化项目特有的发布与投票约束Maven Release InfoMaven 构件如何发布到 Central孵化项目与成熟项目最大的差异在于除了社区dev 列表投票还必须在generalincubator.apache.org上获得 IPMC 成员的binding投票并且发布物根目录必须包含 DISCLAIMER 文件详见第 5 章。1.2 PGP 签名密钥首次担任 Release Manager的成员必须先按 ASF 的 Release Signing 文档与 OpenPGP 指南生成一个专门用于发布签名的 PGP 密钥。仓库 website/community/release/release-version.md 给出了从安装到上传的完整操作步骤。1.2.1 安装 GnuPG 2.x建议安装你所在操作系统对应的GnuPG 2.x尽量使用最新版。例如 Debian/Ubuntu 系apt-get install gnupg21.2.2 生成密钥使用你的Apache ID形如你的Apache IDapache.org作为用户标识USER-ID生成新密钥gpg --full-gen-key交互过程示例不同 GnuPG 版本界面略有差异$ gpg --full-gen-key gpg (GnuPG) 2.4.8; Copyright (C) 2025 g10 Code GmbH This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Please select what kind of key you want: (1) RSA and RSA (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) (9) ECC (sign and encrypt) *default* (10) ECC (sign only) (14) Existing key from card Your selection? 1 RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (3072) 4096 Requested keysize is 4096 bits Please specify how long the key should be valid. 0 key does not expire n key expires in n days nw key expires in n weeks nm key expires in n months ny key expires in n years Key is valid for? (0) 0 Key does not expire at all Is this correct? (y/N) y Real name: (use your Apache ID) Email address: (use your Apache email) Comment: (enter a comment) You selected this USER-ID: Username (Comment) emailaddress Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o配置要点密钥类型根据 gpg 版本选择安全类型至少推荐RSA and RSA密钥长度推荐 4096 位有效期可设为永不过期也可按需设置有效期Real name使用你的 Apache IDEmail address使用你的 Apache 邮箱Comment可添加备注信息。确认后输入保护密钥的口令passphrase┌─────────────────────────────────────────────────────────────┐ │ Please enter the passphrase to │ │ protect your new key │ │ │ │ Passphrases match. │ │ │ │ Passphrase: _______________________________________________ │ │ │ │ Repeat: ___________________________________________________ │ │ ┌─────────────────────────────────────────────────────────┐ │ │ │ │ │ │ └─────────────────────────────────────────────────────────┘ │ │ OK Cancel │ └─────────────────────────────────────────────────────────────┘1.2.3 查看密钥gpg --list-signatures --keyid-format LONG执行后本地所有密钥都会被列出按你的Apache IDapache.org定位到目标密钥。1.2.4 上传公钥到密钥服务器示例输出$ gpg --list-signatures --keyid-format LONG [keyboxd] --------- pub rsa4096/85E2C3CA72D5936C 2025-12-15 [SC] D71C9B1CA898A2408D55EDC785E2C3CA72D5936C uid [ultimate] XXXXX xxxapache.org sig 3 85E2C3CA72D5936C 2025-12-15 [self-signature] sub rsa4096/DF02F738216EBD6D 2025-12-15 [E] sig 85E2C3CA72D5936C 2025-12-15 [self-signature]上例中的85E2C3CA72D5936C即需要上传的key-id。将公钥上传到 GPG 密钥服务器gpg --keyserver keys.openpgp.org --send-key key-id # 示例 # gpg --keyserver keys.openpgp.org --send-key 85E2C3CA72D5936Ckeys.openpgp.org只是随机选择的服务器也可以使用keyserver.ubuntu.com等任意可用服务器。命令失败时可改为通过网页手动上传公钥。上传完成后通常约 1 分钟生效校验密钥是否成功创建若未成功可多次重试# 检查密钥是否创建成功 gpg --keyserver keyserver.ubuntu.com --recv-keys key-id示例$ gpg --keyserver keyserver.ubuntu.com --recv-keys 85E2C3CA72D5936C gpg: key 85E2C3CA72D5936C: XXXXXX xxxxxxapache.org not changed gpg: Total number processed: 1 gpg: unchanged: 1也可以在 OpenPGP Keyserver 网页输入key-id点击Search key按钮确认存在对应名称的密钥。1.2.5 上传到 GitHub建议把 GPG 公钥同步上传到与你的 Apache ID 关联的 GitHub 账户访问 GitHub 的settings/keys页面添加 GPG 密钥如果添加后显示 Unverified需要把 GPG 密钥中使用的邮箱绑定到你的 GitHub 账户。2. 发起发布讨论Discussion正式动手之前必须先向 DEV 邮件列表发送邮件发起下一版本的发布讨论这是 ASF「社区驱动、公开透明」原则的直接体现。收件人Todevfesod.apache.org主题Subject[DISCUSS] Release Apache Fesod(Incubating) ${RELEASE_VERSION}正文BodyHi Community, This is a call for a discussion to release Apache Fesod(Incubating) ${RELEASE_VERSION}. The change lists about this release: https://github.com/apache/fesod/compare/2.0.0-incubating...2.0.1-incubating-rc1 Please leave your comments here about this release plan. We will bump the version in repo and start the release process after the discussion. Best regards, ${RELEASE_MANAGER}占位符说明${RELEASE_VERSION}替换为下一个要发布的版本号${RELEASE_MANAGER}通常为本版本的发布负责人Release Manager。讨论达成一致后仓库中的版本号才会被提升并进入正式发布流程。仓库 pom.xml 中当前版本为2.1.0-incubatingrevision属性并已设置project.build.outputTimestamp可作为版本演进的实际参考。3. 发布材料准备Material Preparation3.1 KEYS 文件如果你是首次担任 Release Manager或原密钥已过期需要将公钥追加到 Apache SVN 项目release仓库中的KEYS文件里。KEYS 文件只在一个权威位置release 目录维护从而保证一致并供 downloads.apache.org 上的签名校验使用Release 仓库https://dist.apache.org/repos/dist/release/incubator/fesod操作步骤# Check out to the local fesod-release directory svn co https://dist.apache.org/repos/dist/release/incubator/fesod/ fesod-release # Enter the local directory cd fesod-release # Export and append to the KEYS file (gpg --list-sigs xxxapache.org gpg --export --armor xxxapache.org) KEYS # Commit svn ci -m add gpg key for xxx注意事项不要直接覆盖仓库中的KEYS文件只能追加KEYS文件只在release目录维护单一事实来源不要在 dev 目录另建副本否则两份副本容易漂移失同步SVN 仓库需要 PPMC 权限可由 PPMC 成员协助完成上传。3.2 POM 配置为将发布推送到 ASF Nexus 仓库需要配置本地 POM 文件。3.2.1 项目配置确保项目的pom.xml配置了 ASF 父 POM。仓库根 pom.xml 正是这样配置的parent groupIdorg.apache/groupId artifactIdapache/artifactId version31/version /parent3.2.2 Maven Settings在本地 Apache Maven 配置文件settings.xml中配置你的 Apache ID 与 GPG 密钥信息settings profiles profile idapache-release/id properties mavenExecutorIdforked-path/mavenExecutorId !-- gpg key-id -- gpg.keynameyourKeyName/gpg.keyname deploy.urlhttps://dist.apache.org/repos/dist/dev/incubator/fesod//deploy.url /properties /profile /profiles servers !-- Apache ID and password -- server idapache.snapshots.https/id usernameyourApacheID/username passwordyourApachePassword/password /server server idapache.releases.https/id usernameyourApacheID/username passwordyourApachePassword/password /server !-- gpg passphrase -- server idgpg.passphrase/id passphraseyourKeyPassword/passphrase /server /servers /settings各配置项说明mavenExecutorIdforked-path以 fork 方式执行 Maven 发布相关插件gpg.keyname指定签名使用的 GPG key-id对应你生成的发布密钥deploy.urldeploy 阶段推送的目标路径这里是 dev 目录RC 产物存放处apache.snapshots.https/apache.releases.https分别为快照与正式版本发布用的 Nexus 账号认证gpg.passphraseGPG 密钥口令供签名插件使用。建议对配置中的口令进行加密存储参考 ASF 的 Maven 构件发布指南与 Maven 口令加密指南。3.3 发布产物Release Artifacts3.3.1 预发布版本Pre-Release以发布2.0.0-incubating为例步骤如下新建分支2.0.0-incubating作为发布分支更新pom.xml中的版本号为2.0.0-incubating在pom.xml中设置固定的project.build.outputTimestamp以确保可重复构建推送 RCRelease Candidate版本标签。# 切换到发布分支 git checkout -b 2.0.0-incubating # 创建 RC1 版本标签 git tag -s 2.0.0-incubating-rc1 -m release: release for 2.0.0-incubating RC1 # 推送标签到远程仓库 git push origin 2.0.0-incubating-rc1更新版本时同时设置固定构建时间戳# 设置固定构建时间戳使每次构建产物完全一致 mvn versions:set-property -Dpropertyproject.build.outputTimestamp -DnewVersion2026-09-10T00:00:00Z # 或直接编辑 pom.xml # project.build.outputTimestamp2026-09-10T00:00:00Z/project.build.outputTimestamp仓库 pom.xml 中已实际设置了project.build.outputTimestamp2026-09-10T00:00:00Z这正是可重复构建Reproducible Builds的落地配置——每次构建都会产出字节级一致的 jar便于社区对发布产物进行可信校验。3.3.2 推送二进制包编译预发布 RC 分支源码并将二进制包推送到 staging 仓库mvn clean deploy -Papache-release -DskipTests -Dgpg.skipfalse参数解读-Papache-release激活settings.xml中定义的apache-releaseprofile指定签名密钥与 deploy 目标-DskipTests发布阶段跳过单元测试-Dgpg.skipfalse强制启用 GPG 签名防止误用-Dgpg.skiptrue导致产物无签名。随后用 Apache ID 登录 ASF Nexus 仓库找到已发布的版本点击Close。若 Close 操作失败很可能是因为签名密钥对应的公钥无法从keys.openpgp.org检索到。请自行到 OpenPGP Keyserver 页面检查。3.3.3 打包源码:::warning 不要在你的日常工作目录中打包 :::本地文件如node_modules、IDE 配置文件如.idea/.vscode、重构后遗留的空目录可能被意外打进source-release.zip引发合规问题例如分发未经授权的二进制文件导致投票失败。必须在全新克隆的 Git 仓库中执行发布流程确保构建产物可复现且干净。注意不要用 IDE如 IntelliJ 或 VS Code打开源码目录以免生成配置文件或编译缓存直接在终端中执行 Maven 发布命令。使用git archive确保源码包干净排除.git目录及其它被忽略的文件git archive --formattar.gz \ --prefixapache-fesod-2.0.0-incubating-src/ \ -o apache-fesod-2.0.0-incubating-src.tar.gz \ e7546d1138d4d3a638df10193a4c29c50a7e55d8注意上例中的哈希e7546d1138d4d3a638df10193a4c29c50a7e55d8对应标签2.0.0-incubating-rc1的 commit 哈希。--prefix参数保证解压后文件位于带版本号的目录下避免散落污染。3.3.4 签名对生成的源码包执行 GPG 签名与 SHA512 校验和计算# 1. 用指定 GPG key-id 对源码包签名生成 .asc # 将 key-id 替换为你的 GPG key-id for i in *.tar.gz; do echo Signing $i; gpg -u key-id --armor --output $i.asc --detach-sig $i ; done # 2. 生成 SHA512 校验和.sha512 for i in *.tar.gz; do echo Hashing $i; sha512sum $i $i.sha512 ; done签名完成后可在本地先行验证# 验证签名 for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done # 验证 SHA512 for i in *.tar.gz; do echo $i; sha512sum --check $i.sha512; done3.3.5 上传到 SVN将签好名的源码包上传到 SVN dev 仓库# Check out the SVN dev repository svn co https://dist.apache.org/repos/dist/dev/incubator/fesod/ fesod-dev cd fesod-dev # 创建版本目录 mkdir 2.0.0-incubating-rc1 cd 2.0.0-incubating-rc1 # 复制源码包文件假设它们在父目录中 cp ../../apache-fesod-2.0.0-incubating-src.tar.gz . cp ../../apache-fesod-2.0.0-incubating-src.tar.gz.asc . cp ../../apache-fesod-2.0.0-incubating-src.tar.gz.sha512 . # 提交到 SVN cd .. svn add 2.0.0-incubating-rc1 svn commit -m Add 2.0.0-incubating-rc1 source release你需要先配置 SVN 用户也可以每条命令中直接指定用户名与密码svn co --username apache-id --password password如果出现意外文件或错误请删除相关内容执行svn delete然后按上述流程重新上传。4. 社区投票Community Vote每个版本可能经历多轮投票RCN与 Round N 均表示第 N 轮即该版本的第 N 次投票。4.1 发起投票收件人Todevfesod.apache.org主题Subject[VOTE] Release Apache Fesod (Incubating) ${RELEASE_VERSION}-RCN正文BodyHi Community, This is a call for vote to release Apache Fesod(Incubating) ${RELEASE_VERSION}. The release candidates: https://dist.apache.org/repos/dist/dev/incubator/fesod/${RELEASE_VERSION}-RCN The staging repo: https://repository.apache.org/content/repositories/orgapachefesod-1016 Git tag for the release: https://github.com/apache/fesod/releases/tag/${RELEASE_VERSION}-RCN Hash for the release tag: e7546d1138d4d3a638df10193a4c29c50a7e55d8 Release Notes: https://github.com/apache/fesod/releases/tag/${RELEASE_VERSION}-RCN The artifacts have been signed with Key [ key-id ], corresponding to [ xxxapache.org ] 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 , please see https://fesod.apache.org/需将正文中的${RELEASE_VERSION}与RCN轮次信息替换为实际值。邮件中提到的构建环境./mvnw clean package -DskipTests可直接在仓库中执行——仓库根目录自带 Maven Wrappermvnw 与 mvnw.cmd无需预先安装特定版本的 Maven。4.2 关闭投票投票至少开放 72 小时且获得至少 3 个 binding 的 1 票后公布投票结果收件人Todevfesod.apache.org主题Subject[RESULT][VOTE] Release Apache Fesod (Incubating) ${RELEASE_VERSION}-RCN正文BodyHi Community, The vote to release Apache Fesod (Incubating) ${RELEASE_VERSION}-RCN has PASSED and closed now. The result is as follows: 3 binding 1 Votes: - XXX - XXX - XXX 2 non-binding 1 Votes: - XXX - XXX no further 0 or -1 votes. The vote thread: https://lists.apache.org/thread/3b8vz8891cjtjblthvnx95l44sh2fmqz Thank you for reviewing and voting for our release candidate. We will now bring this vote to the generalincubator mailing list for IPMC approval.如果投票失败先解决提出的问题再按发布流程准备新一轮RCN材料并重新发起投票。5. 孵化器投票Incubator Vote社区投票通过并结束后必须在孵化器邮件列表上发起投票。这是孵化项目独有的环节由IPMCIncubator PMC成员行使 binding 投票权。5.1 发起投票与发起社区投票类似但需要附上社区投票线程链接证明社区内部已达成共识。收件人Togeneralincubator.apache.org主题Subject[VOTE] Release Apache Fesod (Incubating) ${RELEASE_VERSION}-RCN正文BodyHi all, This is a call for vote to release Apache Fesod(Incubating) ${RELEASE_VERSION}-RCN. The Apache Fesod community has voted and approved the release of Apache Fesod(Incubating) ${RELEASE_VERSION}. We now kindly request the IPMC members review and vote for this release. Project description: Apache Fesod (Incubating) is a high-performance, easy-to-use Java library for processing spreadsheet files. The vote thread: https://lists.apache.org/thread/r6hsbb9tmsqmn9s7q9qptv3z287lkcbf The vote result thread: https://lists.apache.org/thread/r6hsbb9tmsqmn9s7q9qptv3z287lkcbf The release candidates: https://dist.apache.org/repos/dist/dev/incubator/fesod/x.x.x/ The staging repository: https://repository.apache.org/content/repositories/${STAGING.RELEASE}/ Git tag for the release: https://github.com/apache/fesod/releases/tag/vx.x.x Hash for the release tag: ea6687ff9da3d3389c51a39852d84f3a209708c4 Release Notes: https://github.com/apache/fesod/releases/tag/vx.x.x The artifacts have been signed with Key [ key-id ], corresponding to [ xxxxapache.org ] 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 , please see https://fesod.apache.org/5.2 公布孵化器投票结果投票至少开放 72 小时且获得至少 3 个 binding 的 1 票后公布结果收件人Togeneralincubator.apache.org主题Subject[RESULT][VOTE] Release Apache Fesod (Incubating) ${RELEASE_VERSION}-RCN正文BodyHi Incubator PMC, The vote to release Apache Fesod(Incubating) ${RELEASE_VERSION}-RCN has passed with 3 1 binding and 1 1 non-binding votes, no 0 or -1 votes. Binding votes: - XXX - XXX - XXX Non-Binding votes: - XXX Vote thread: https://lists.apache.org/thread/o7vwdvtolclcv1y4j4ozshj923ppwlnl Thanks for reviewing and voting for our release candidate. We will proceed with publishing the approved artifacts and sending out the announcement soon.6. 完成发布Completing the Release6.1 迁移源码与二进制包登录 Apache Nexus 仓库选中之前 Close 的orgapachefesod-XXX仓库点击Release图标完成发布。将签名文件、src 与 bin 从 dev 迁移到 release 路径svn mv https://dist.apache.org/repos/dist/dev/incubator/fesod/x.x.x-RCN https://dist.apache.org/repos/dist/release/incubator/fesod/x.x.x -m Release X.X.X将上一个版本 Release Note 设置为最新Set as the latest release并提交在 Fesod 网站上更新 x.x.x 版本的文档并补充对应的二进制与源码下载链接。发布后的版本会体现在仓库的下载文档中。仓库 website/docs/download.md 的「Latest Stable Release」表格即展示当前最新版本2.0.2-incubating含apache-fesod-2.0.2-incubating-src.tar.gz、.asc签名与.sha512校验文件历史归档版本则列出2.0.1-incubating与2.0.0-incubating这正是本节流程的实际产物。6.2 发布公告收件人Toannounceapache.org,devfesod.apache.org主题Subject[ANNOUNCE] Apache Fesod(Incubating) ${RELEASE_VERSION} released正文BodyHello everyone, The Apache Fesod(Incubating) ${RELEASE_VERSION} has been released! Apache Fesod is an easy-to-use, high-performance, open source distributed transaction solution. Download Links: https://fesod.apache.org/download/fesod/ Release Notes: https://github.com/apache/fesod/releases/tag/x.x.x/ Website: https://fesod.apache.org/ Resources: - Issue: https://github.com/apache/fesod/issues - Mailing list: devfesod.apache.org We would like to thank all the contributors who made this release possible, and to our Incubator mentors for their great guidance. ${RELEASE_MANAGER} On behalf of Apache Fesod (Incubating) PPMC仓库中的实际发布公告可作为模板参考例如 website/blog/2026-02-27-apache-fesod-2-0-1-incubating-released.md 记录了 2.0.1-incubating 作为 Fesod 加入 ASF 孵化器后首个官方版本的发布内容包括多模块架构重构、JDK 25 支持、afterSheetDispose生命周期方法、Header Merge Strategy、每日 fuzz 测试、依赖安全升级等。附发布产物合规性验证速查发布流程中的产物合规要求可以借助仓库本身验证。结合 website/community/release/verify-release.md 的核对清单DISCLAIMER孵化项目根目录必须存在 DISCLAIMER 文件声明项目正处于 ASF 孵化期LICENSE / NOTICE根目录 LICENSE 必须包含 Apache License 2.0NOTICE 需包含当前版权年份如 2025-2026以及对捆绑依赖如基于 Alibaba EasyExcel 的声明的必要署名ASF License Header所有.java、.xml、.yml等源码文件需带 ASF 头。仓库通过 licenserc.tomlSpotless 插件apache-rat:check的配套配置与根 pom.xml 中apache-rat-plugin的 excludes 配置如排除website/**、**/*.md、**/*.xlsx等实现自动化 License Header 管理可重复构建project.build.outputTimestamp固定后每次构建产物一致编译验证./mvnw clean install -DskipTests仓库内置 mvnw 包装器且当前版本支持 JDK 8详见 website/docs/quickstart/guide.md 中的版本支持表。将上述检查项逐条勾选后即可放心地在投票邮件中投出 1 票。结语Apache FesodIncubating的发布流程以「公开讨论 → 材料准备 → 社区投票 → IPMC 投票 → 正式发布」为主线环环相扣PGP 密钥与 KEYS 文件保证签名可信git archive 固定outputTimestamp保证源码包干净可复现72 小时投票窗口与 binding 票门槛保证社区共识最后的svn mv与公告完成归档闭环。本文所有命令与配置均可直接套用到仓库 website/community/release/release-version.md 描述的流程中每次 Fesod 新版本的发布都是这套「Apache Way」流程的一次完整实践。赞分享后端【免费下载链接】fesodFast. Easy. Done. Processing spreadsheets without worrying about large files causing OOM.项目地址https://gitcode.com/gh_mirrors/fast/fesod点击查看免费下载相关推荐为什么你关掉的 Windows Defender 总在重启后复活答案藏在一个开源工具里为什么你关掉的 Windows Defender 总在重启后复活答案藏在一个开源工具里 你大概也经历过这个死循环在设置里关掉实时保护第二天它满血复活照着后端Apache TVM 发布流程全指南从 Release Candidate 投票到正式版本发布的完整实践Apache TVM 发布流程全指南从 Release Candidate 投票到正式版本发布的完整实践 TVM 作为 Apache 软件基金会ASF顶级编译器深度学习模型优化Apache DolphinScheduler 版本发布全流程指南GPG 签名、Maven 发布、SVN 上传与社区投票Apache DolphinScheduler 版本发布全流程指南GPG 签名、Maven 发布、SVN 上传与社区投票 Apache DolphinSche任务调度大数据后端前端上一篇IngressMonitorController故障排查指南常见问题与解决方案下一篇Nuklear UI渲染调试指南5个实战技巧解决即时模式GUI开发难题创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考