同步操作将从 OpenHarmony/third_party_harfbuzz 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
HarfBuzz release walk-through checklist:
Open gitk and review changes since last release.
git diff $(git describe | sed 's/-.*//').. src/*.h
prints all public API
changes.
Document them in NEWS. All API and API semantic changes should be clearly marked as API additions, API changes, or API deletions. Document deprecations. Ensure all new API / deprecations are in listed correctly in docs/harfbuzz-sections.txt. If release added new API, add entry for new API index at the end of docs/harfbuzz-docs.xml.
If there's a backward-incompatible API change (including deletions for API used anywhere), that's a release blocker. Do NOT release.
Based on severity of changes, decide whether it's a minor or micro release number bump,
Search for REPLACEME on the repository and replace it with the chosen version for the release.
Make sure you have correct date and new version at the top of NEWS file.
Bump version in line 3 of meson.build and configure.ac.
Do a meson test -Cbuild
so it both checks the tests and updates
hb-version.h (use git diff
to see if is really updated).
Commit NEWS, meson.build, configure.ac, and src/hb-version.h, as well as any REPLACEME changes you made. The commit message is simply the release number. Eg. "1.4.7"
Do a meson dist -Cbuild
that runs the tests against the latest commited changes.
If doesn't pass, something fishy is going on, reset the repo and start over.
Tag the release and sign it: Eg. "git tag -s 1.4.7 -m 1.4.7". Enter your GPG password.
Build win32 bundle. See README.mingw.md.
Push the commit and tag out: "git push --follow-tags".
Go to GitHub release page here, edit the tag, upload win32 bundle and NEWS entry and save. No need to upload source tarball as we rely to GitHub's automatic tar.gz generation.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。