What
Cut and publish release candidate 2025-1-RC5, reflecting the terminology
and bibliography alignment merged in #267 (ISO/IEC FDIS 20151-1, ISO/IEC
38500:2024, ISO/IEC 7498-1:1994).
Steps
⚠️ Merge method for the release-prep PR
This PR must be merged with "Rebase and merge", not "Squash and merge".
The release-prep branch carries two commits on purpose: one that flips
specStatus to "base" and sets publishDate (this is the commit the git
tag needs to point at), and a second that reverts specStatus back to
"unofficial". Squashing collapses both into a single final-state commit and
silently drops the "base"-status snapshot that the tag requires.
This isn't hypothetical — it already happened once for 2025-1-RC4: PR #206
was squash-merged, which ate the intermediate commit, had to be reverted
(commit fee40e5), and was redone as two individually preserved commits
(7c8f678, 6b3df2a) before the tag would build correctly.
What
Cut and publish release candidate
2025-1-RC5, reflecting the terminologyand bibliography alignment merged in #267 (ISO/IEC FDIS 20151-1, ISO/IEC
38500:2024, ISO/IEC 7498-1:1994).
Steps
release/2025-1-rc5→main)chore: publish 2025-1-RC5commit as2025-1-RC5and push the tagThis PR must be merged with "Rebase and merge", not "Squash and merge".
The release-prep branch carries two commits on purpose: one that flips
specStatusto"base"and setspublishDate(this is the commit the gittag needs to point at), and a second that reverts
specStatusback to"unofficial". Squashing collapses both into a single final-state commit andsilently drops the
"base"-status snapshot that the tag requires.This isn't hypothetical — it already happened once for
2025-1-RC4: PR #206was squash-merged, which ate the intermediate commit, had to be reverted
(commit
fee40e5), and was redone as two individually preserved commits(
7c8f678,6b3df2a) before the tag would build correctly.