The S3 upload step can be skipped by providing the validate argument to the build script.
The build process can be configured using the .smpte-build.json file which is contains a JSON object that
- conforms to the JSON schema at .
The build process MAY be configured using an optional .smpte-build.json file containing a JSON object that
+ conforms to the JSON schema at . When the file is absent, the build derives
+ its configuration from the document metadata and the repository's git tags.
.smpte-build.json..smpte-build.json.If present or not equal to null, the latestEditionTag property contains the Git tag or commit
- that is used when generating a redline against the latest published edition of the document.
If present and not equal to null, the latestEditionTag property overrides the auto-selected
+ redline base with the specified Git tag or commit. When absent or null, the redline base is auto-selected as
+ described in .
- For further explanation of determining the value of latestEditionTag, see
+ For further explanation of how the redline base is determined, see .
meta tags to Document Status
- Whenever the state of the document changes to <meta itemprop="pubState" content="pub" /> on the main branch, then a release shall be created in the GitHub repo.
+ Whenever the state of the document changes to <meta itemprop="pubState" content="pub" /> on the main branch, the tooling automatically creates a draft release in the GitHub repo. An authorized editor reviews and publishes the draft to finalize the release and trigger production of the associated artifacts.
- Both the GitHub release and git tag shall be named YYYYMMDD "-" pubStage. The YYYYMMDD should directly represent the value used in pubDateTime as defined in .
+ Both the GitHub release and the git tag shall be named YYYYMMDD "-" pubStage, where YYYYMMDD directly represents the value of pubDateTime (as defined in ) and the pubStage suffix is the value of the pubStage meta in lowercase.
20230615-fcd or 20230925-pub
- The latestEditionTag property in the .smpte-build.json file shall always be equal to the name of the most recent git tag. This will trigger the tooling to create a link for Redline to most recent edition during any PRs and merges to the main branch.
+ The tooling determines the redline base automatically. When pubStage is PUB, the redline is generated against the most recent prior -pub tag (the previous edition); for any other pubStage, the redline is generated against the most recent prior dated tag of any stage (iterative draft-to-draft). The Redline to most recent edition link is generated for every PR and merge to main without manual configuration. If no prior matching tag exists, the redline is omitted. A latestEditionTag value MAY be set in .smpte-build.json to override the auto-selected base — for example, when rebuilding an archived edition or pinning to a specific historical release.
- The tooling will automatically generate zip file packages within the release details page, to be used for both :
-See https://github.com/SMPTE/st428-24-private/releases/tag/20241101-dp, where https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/27c-st-428-24-dp-2024-12-06-pub.zip (ballot zip), and https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/20241101-dp.zip (publish zip) are available.
- + For workflow events that share bothpubDateTime and pubStage with the most recent release but represent a distinct release moment (e.g., entering the PCD period from a Pre-FCD review on the same day), the merge commit message shall include the token [force-release]. The tooling appends a numeric suffix (-2, -3, …) to the tag to disambiguate.
+
+ + Publishing the draft release triggers the tooling to automatically generate zip file packages and attach them to the release details page, used for: +
+ ++ See https://github.com/SMPTE/st428-24-private/releases/tag/20241101-dp, where https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/27c-st-428-24-dp-2024-12-06-pub.zip (ballot zip) and https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/20241101-dp.zip (publish zip) are available. +
- See for a sample workflow utilizing releases. + See for a sample workflow utilizing releases.
For workflow events that share both pubDateTime and pubStage with the most recent release but represent a distinct release moment (e.g., entering the PCD period from a Pre-FCD review on the same day), the merge commit message shall include the token [force-release]. The tooling appends a numeric suffix (-2, -3, …) to the tag to disambiguate.
+ To publish the draft release after it has been auto-created: +
+https://github.com/{org}/{repo}/releases).YYYYMMDD-pubStage tag for the merged document state.Publishing the draft release triggers the tooling to automatically generate zip file packages and attach them to the release details page, used for:
From 0f2410025ddc8fc088e80adc5a7b20d305295189 Mon Sep 17 00:00:00 2001 From: Steve LLamb <38917682+SteveLLamb@users.noreply.github.com> Date: Thu, 30 Apr 2026 09:50:26 -0700 Subject: [PATCH 3/7] seperate out redline from releases and published editions --- doc/main.html | 39 +++++++++++++++++-- scripts/build.mjs | 98 +++++++++++++++++++++++++++++++++-------------- 2 files changed, 104 insertions(+), 33 deletions(-) diff --git a/doc/main.html b/doc/main.html index f621979..4e4b08d 100644 --- a/doc/main.html +++ b/doc/main.html @@ -1649,15 +1649,15 @@If present and not equal to null, the latestEditionTag property overrides the auto-selected
- redline base with the specified Git tag or commit. When absent or null, the redline base is auto-selected as
- described in .
null, the base is
+ auto-selected as described in .
- For further explanation of how the redline base is determined, see . + For the complete description of redline outputs produced by the tooling, see .
@@ -1698,6 +1698,37 @@The tooling automatically produces redline (change-tracked) renderings of the document on every build — pull requests, merges to main, and release publications. Redlines compare the current rendered document against a chosen reference rendering using the htmldiff utility, and the resulting HTML files are deployed to S3 alongside the clean output and bundled into the review zip when applicable.
Three redlines may be produced per build, each with a different reference base:
+ +base-rl.html)Generated against the pull request's target branch (typically main), via the GITHUB_BASE_REF environment variable provided by GitHub Actions on pull request events. Shows what the PR itself changes relative to the branch it will merge into.
Generated: on pull request events. Omitted: on push and release events, where no PR base is defined.
+pub-rl.html)Generated against the most recent prior git tag matching YYYYMMDD-pub — the previous published edition. Shows what has changed since the last edition was published. The reference base may be overridden by setting latestEditionTag in .smpte-build.json — useful when rebuilding an archived edition or pinning to a specific historical release.
Generated: on every event. Omitted: when no prior -pub tag exists (e.g., the first edition).
release-rl.html)Generated against the most recent prior git tag matching YYYYMMDD-{stage} for any recognized pubStage (-wd, -cd, -fcd, -dp, or -pub). Shows iterative changes since the last release tag of any kind, supporting draft-to-draft review across the workflow stages defined in .
Generated: on every event. Omitted: when no prior dated release tag exists. May coincide with the published-edition redline when no draft tags exist between published editions.
+In all cases, any tag pointing at the HEAD commit is excluded from selection, so a freshly-tagged release does not redline against itself. When the build runs on a pull request, links to all available redline outputs are included in the comment posted to the PR (see ). When the build runs on a release publication, the redline files are bundled into the review zip attached to the release (see ).
20230615-fcd or 20230925-pub
- The tooling determines the redline base automatically. When pubStage is PUB, the redline is generated against the most recent prior -pub tag (the previous edition); for any other pubStage, the redline is generated against the most recent prior dated tag of any stage (iterative draft-to-draft). The Redline to most recent edition link is generated for every PR and merge to main without manual configuration. If no prior matching tag exists, the redline is omitted. A latestEditionTag value MAY be set in .smpte-build.json to override the auto-selected base — for example, when rebuilding an archived edition or pinning to a specific historical release.
+ Both the published-edition redline (pub-rl.html) and the most-recent-release redline (release-rl.html) are bundled into the review zip attached to the release. See for the complete description of the redline outputs the tooling produces and how their reference bases are chosen.
For workflow events that share both pubDateTime and pubStage with the most recent release but represent a distinct release moment (e.g., entering the PCD period from a Pre-FCD review on the same day), the merge commit message shall include the token [force-release]. The tooling appends a numeric suffix (-2, -3, …) to the tag to disambiguate.
diff --git a/scripts/build.mjs b/scripts/build.mjs
index ac114da..29626d5 100644
--- a/scripts/build.mjs
+++ b/scripts/build.mjs
@@ -157,7 +157,7 @@ function mirrorDirExcludeTooling(srcDir, targetDir, relParentPath) {
}
-async function build(buildPaths, baseRef, lastEdRef, docMetadata) {
+async function build(buildPaths, baseRef, lastEdRef, lastReleaseRef, docMetadata) {
const generatedFiles = {};
@@ -197,19 +197,34 @@ async function build(buildPaths, baseRef, lastEdRef, docMetadata) {
}
- /* generate pub redline, if requested */
-
- if (lastEdRef !== null) {
+ /* fetch tags once for both pub and release redlines */
+ if (lastEdRef !== null || lastReleaseRef !== null) {
child_process.execSync(`git fetch --tags`);
+ }
+
+ /* generate redline against most recent published edition, if requested */
+
+ if (lastEdRef !== null) {
- console.log(`Generating a redline against the latest edition tag: ${lastEdRef}.`);
+ console.log(`Generating a redline against the latest published edition tag: ${lastEdRef}.`);
await generateRedline(buildPaths, lastEdRef, buildPaths.pubRedLineRefPath, buildPaths.pubRedlinePath);
generatedFiles.pubRedline = buildPaths.pubRedlineName;
}
+ /* generate redline against most recent release tag, if requested */
+
+ if (lastReleaseRef !== null) {
+
+ console.log(`Generating a redline against the latest release tag: ${lastReleaseRef}.`);
+
+ await generateRedline(buildPaths, lastReleaseRef, buildPaths.releaseRedLineRefPath, buildPaths.releaseRedlinePath);
+ generatedFiles.releaseRedline = buildPaths.releaseRedlineName;
+
+ }
+
return generatedFiles;
}
@@ -245,7 +260,10 @@ async function generatePubLinks(buildPaths, pubLinks) {
linksDocContents += `[Redline to current draft](${pubLinks.baseRedline})\n`;
if ("pubRedline" in pubLinks)
- linksDocContents += `[Redline to most recent edition](${pubLinks.pubRedline})\n`;
+ linksDocContents += `[Redline to most recent published edition](${pubLinks.pubRedline})\n`;
+
+ if ("releaseRedline" in pubLinks)
+ linksDocContents += `[Redline to most recent release](${pubLinks.releaseRedline})\n`;
if ("reviewZip" in pubLinks)
linksDocContents += `[ZIP package](${pubLinks.reviewZip})\n`;
@@ -297,6 +315,10 @@ async function s3Upload(buildPaths, versionKey, generatedFiles) {
pubLinks.pubRedline = `${deployPrefix}${s3PubKeyPrefix}${encodeURIComponent(generatedFiles.pubRedline)}`;
}
+ if ("releaseRedline" in generatedFiles) {
+ pubLinks.releaseRedline = `${deployPrefix}${s3PubKeyPrefix}${encodeURIComponent(generatedFiles.releaseRedline)}`;
+ }
+
if ("reviewZip" in generatedFiles) {
pubLinks.reviewZip = `${deployPrefix}${s3PubKeyPrefix}${encodeURIComponent(generatedFiles.reviewZip)}`;
}
@@ -334,6 +356,9 @@ async function makeReviewZip(buildPaths, generatedFiles, docMetadata) {
if ("pubRedline" in generatedFiles)
zip.addLocalFile(path.join(buildPaths.pubDirPath, generatedFiles.pubRedline));
+ if ("releaseRedline" in generatedFiles)
+ zip.addLocalFile(path.join(buildPaths.pubDirPath, generatedFiles.releaseRedline));
+
/* create zip filename */
const comps = [];
@@ -383,7 +408,11 @@ async function makePubArtifacts(buildPaths, generatedFiles, docMetadata) {
}
if ("pubRedline" in generatedFiles) {
- htmlLinks += `
Redline to most recent edition
\n`; + htmlLinks += `Redline to most recent published edition
\n`; + } + + if ("releaseRedline" in generatedFiles) { + htmlLinks += `Redline to most recent release
\n`; } if (generatedFiles.reviewZip !== undefined) { @@ -655,6 +684,10 @@ class BuildPaths { this.pubRedlinePath = path.join(this.pubDirPath, this.pubRedlineName); this.pubRedLineRefPath = path.join(this.buildDirPath, this.pubRedlineName); + this.releaseRedlineName = "release-rl.html"; + this.releaseRedlinePath = path.join(this.pubDirPath, this.releaseRedlineName); + this.releaseRedLineRefPath = path.join(this.buildDirPath, this.releaseRedlineName); + this.baseRedlineName = "base-rl.html"; this.baseRedlinePath = path.join(this.pubDirPath, this.baseRedlineName); this.baseRedLineRefPath = path.join(this.buildDirPath, this.baseRedlineName); @@ -679,41 +712,47 @@ class BuildConfig { } const DATED_TAG_RE = /^\d{8}-(pub|fcd|cd|wd|dp)$/; +const PUB_TAG_RE = /^\d{8}-pub$/; -function deriveLastEdRef(pubStage, override) { - if (override !== null && override !== undefined && override !== "") { - return override; +function getHeadTags() { + try { + return new Set( + child_process.execSync("git tag --points-at HEAD") + .toString() + .split("\n") + .map(t => t.trim()) + .filter(Boolean) + ); + } catch { + return new Set(); } +} - const editionOnly = pubStage === "PUB"; - const globs = editionOnly ? ["*-pub"] : ["*-pub", "*-fcd", "*-cd", "*-wd", "*-dp"]; - +function pickLatestTag(globs, filterRe) { let allTags; try { allTags = child_process.execSync(`git tag -l ${globs.map(g => `'${g}'`).join(" ")} --sort=-version:refname`) .toString() .split("\n") .map(t => t.trim()) - .filter(t => DATED_TAG_RE.test(t)); + .filter(t => filterRe.test(t)); } catch { return null; } - let headTags; - try { - headTags = new Set( - child_process.execSync("git tag --points-at HEAD") - .toString() - .split("\n") - .map(t => t.trim()) - .filter(Boolean) - ); - } catch { - headTags = new Set(); + const headTags = getHeadTags(); + return allTags.find(t => !headTags.has(t)) || null; +} + +function deriveLastEdRef(override) { + if (override !== null && override !== undefined && override !== "") { + return override; } + return pickLatestTag(["*-pub"], PUB_TAG_RE); +} - const candidate = allTags.find(t => !headTags.has(t)); - return candidate || null; +function deriveLastReleaseRef() { + return pickLatestTag(["*-pub", "*-fcd", "*-cd", "*-wd", "*-dp"], DATED_TAG_RE); } async function main() { @@ -840,9 +879,10 @@ async function main() { /* render document */ - const lastEdRef = deriveLastEdRef(docMetadata.pubStage, config.latestEditionTag); + const lastEdRef = deriveLastEdRef(config.latestEditionTag); + const lastReleaseRef = deriveLastReleaseRef(); - Object.assign(generatedFiles, await build(buildPaths, baseRef, lastEdRef, docMetadata)); + Object.assign(generatedFiles, await build(buildPaths, baseRef, lastEdRef, lastReleaseRef, docMetadata)); /* validate rendered document */ From 08c9ba0daabff88892ea3a999c28adff9e8cc37c Mon Sep 17 00:00:00 2001 From: Steve LLamb <38917682+SteveLLamb@users.noreply.github.com> Date: Thu, 30 Apr 2026 10:02:31 -0700 Subject: [PATCH 4/7] add ag-02 refs to redline descriptions --- doc/main.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/main.html b/doc/main.html index 4e4b08d..edd0d34 100644 --- a/doc/main.html +++ b/doc/main.html @@ -1715,12 +1715,14 @@pub-rl.html)Generated against the most recent prior git tag matching YYYYMMDD-pub — the previous published edition. Shows what has changed since the last edition was published. The reference base may be overridden by setting latestEditionTag in .smpte-build.json — useful when rebuilding an archived edition or pinning to a specific historical release.
This redline satisfies the requirement in for a redline against the published document (the baseline draft) when preparing a revision.
Generated: on every event. Omitted: when no prior -pub tag exists (e.g., the first edition).
release-rl.html)Generated against the most recent prior git tag matching YYYYMMDD-{stage} for any recognized pubStage (-wd, -cd, -fcd, -dp, or -pub). Shows iterative changes since the last release tag of any kind, supporting draft-to-draft review across the workflow stages defined in .
This redline satisfies the requirement in that markup from the ballot document be provided for comment resolution.
Generated: on every event. Omitted: when no prior dated release tag exists. May coincide with the published-edition redline when no draft tags exist between published editions.
Generated against the most recent prior git tag matching YYYYMMDD-{stage} for any recognized pubStage (-wd, -cd, -fcd, -dp, or -pub). Shows iterative changes since the last release tag of any kind, supporting draft-to-draft review across the workflow stages defined in .
This redline satisfies the requirement in that markup from the ballot document be provided for comment resolution.
-Generated: on every event. Omitted: when no prior dated release tag exists. May coincide with the published-edition redline when no draft tags exist between published editions.
+Generated: when the current document's pubStage is WD, CD, FCD, or DP. Omitted: when pubStage is PUB (a published edition's relevant comparison is to the prior published edition only) or when no prior dated release tag exists.
pubState
- For further explanation of determining the value of the document's pubState, see
+ For further explanation of determining the value of the document's pubState, see
pubStage
- For further explanation of determining the value of the document's pubStage, see
+ For further explanation of determining the value of the document's pubStage, see
release-rl.html)Generated against the most recent prior git tag matching YYYYMMDD-{stage} for any recognized pubStage (-wd, -cd, -fcd, -dp, or -pub). Shows iterative changes since the last release tag of any kind, supporting draft-to-draft review across the workflow stages defined in .
Generated against the most recent prior git tag matching YYYYMMDD-{stage} for any recognized pubStage (-wd, -cd, -fcd, -dp, or -pub). Shows iterative changes since the last release tag of any kind, supporting draft-to-draft review across the workflow stages defined in .
This redline satisfies the requirement in that markup from the ballot document be provided for comment resolution.
Generated: when the current document's pubStage is WD, CD, FCD, or DP. Omitted: when pubStage is PUB (a published edition's relevant comparison is to the prior published edition only) or when no prior dated release tag exists.
In all cases, any tag pointing at the HEAD commit is excluded from selection, so a freshly-tagged release does not redline against itself. When the build runs on a pull request, links to all available redline outputs are included in the comment posted to the PR (see ). When the build runs on a release publication, the redline files are bundled into the review zip attached to the release (see ).
In all cases, any tag pointing at the HEAD commit is excluded from selection, so a freshly-tagged release does not redline against itself. When the build runs on a pull request, links to all available redline outputs are included in the comment posted to the PR (see ). When the build runs on a release publication, the redline files are bundled into the review zip attached to the release (see ).
meta tags to Document Status
- maps the required content values of pubState, pubStage, and pubConfidential during the various stages of document development. These values represent the naming convention(s) as defined in and flowcharts as defined in
-
| Document Status | -pubStage value |
- pubState value |
- pubConfidential value |
-
|---|---|---|---|
| Initial draft or revision (Working Draft) in:
- Draft Group (DG) - Study Group (SG) - Working Group (WG) |
- WD |
- draft |
- yes |
-
| >> Document moves to TC >> | -|||
| Pre-FCD (Final Committee Draft) review | -WD |
- pub |
- yes |
-
| >> If pre-FCD comments received, back to DG/SG/WG >> | -|||
| Pre-FCD comment resolution ongoing | -CD |
- draft |
- yes |
-
| Pre-FCD comment resolution complete | -CD |
- pub |
- yes |
-
| >> Document moves to TC >> | -|||
| PCD (Public Committee Draft) period | -CD |
- pub |
- no |
-
| PCD comment resolution ongoing (moves back to DG/SG/WG) | -CD |
- draft |
- yes |
-
| PCD comment resolution complete | ->> Back to Pre-FCD (Final Committee Draft) review >> | -||
| (OR) | -|||
| Ready for FCD ballot | -CD |
- pub |
- yes |
-
| FCD ballot period | -CD |
- pub |
- yes |
-
| >> If FCD ballot comments received >> | -|||
| FCD ballot comment resolution ongoing | -FCD |
- draft |
- yes |
-
| FCD ballot comment resolution complete | -FCD |
- pub |
- yes |
-
| Pre-DP (Draft Publication) review | -FCD |
- pub |
- yes |
-
| Pre-DP ballot period | -FCD |
- pub |
- yes |
-
| (ELSE) | -|||
| FCD ballot passes, no comments | -DP |
- pub |
- yes |
-
| DP ballot passes | -DP |
- pub |
- yes |
-
| Ready for ST (Standards Committee) Audit | -DP |
- pub |
- yes |
-
| ST Audit period | -DP |
- pub |
- yes |
-
| ST Audit complete | -PUB |
- draft |
- yes |
-
| Waiting for publication | -PUB |
- draft |
- yes |
-
| Published | -PUB |
- pub |
- no |
-
- See for a sample workflow utilizing these statuses. -
+This annex describes the tooling behavior that auto-drafts GitHub releases. For the document workflow that drives when releases are created and who publishes them, see .
+Whenever the state of the document changes to <meta itemprop="pubState" content="pub" /> on the main branch, the tooling automatically creates a draft release in the GitHub repo. A user with appropriate permissions reviews and publishes the draft to finalize the release and trigger production of the associated artifacts.
- Whenever the state of the document changes to <meta itemprop="pubState" content="pub" /> on the main branch, the tooling automatically creates a draft release in the GitHub repo. An authorized editor reviews and publishes the draft to finalize the release and trigger production of the associated artifacts.
-
- Both the GitHub release and the git tag shall be named YYYYMMDD "-" pubStage, where YYYYMMDD directly represents the value of pubDateTime (as defined in ) and the pubStage suffix is the value of the pubStage meta in lowercase.
-
- 20230615-fcd or 20230925-pub
-
- Both the published-edition redline (pub-rl.html) and the most-recent-release redline (release-rl.html) are bundled into the review zip attached to the release. See for the complete description of the redline outputs the tooling produces and how their reference bases are chosen.
-
- For workflow events that share both pubDateTime and pubStage with the most recent release but represent a distinct release moment (e.g., entering the PCD period from a Pre-FCD review on the same day), the merge commit message shall include the token [force-release]. The tooling appends a numeric suffix (-2, -3, …) to the tag to disambiguate.
-
- To publish the draft release after it has been auto-created: -
+The GitHub release and the git tag shall be named YYYYMMDD "-" pubStage, where YYYYMMDD represents the value of pubDateTime (as defined in ) and the pubStage suffix is the value of the pubStage meta in lowercase.
20230615-fcd or 20230925-pub
For workflow events that share both pubDateTime and pubStage with the most recent release but represent a distinct release moment, the merge commit message shall include the token [force-release]. The tooling appends a numeric suffix (-2, -3, …) to the tag to disambiguate.
To publish a draft release after it has been auto-created:
https://github.com/{org}/{repo}/releases).https://github.com/SMPTE/{repo}/releases).YYYYMMDD-pubStage tag for the merged document state.- Publishing the draft release triggers the tooling to automatically generate zip file packages and attach them to the release details page, used for: -
- -- See https://github.com/SMPTE/st428-24-private/releases/tag/20241101-dp, where https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/27c-st-428-24-dp-2024-12-06-pub.zip (ballot zip) and https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/20241101-dp.zip (publish zip) are available. -
- -
- Generally, no changes to a document shall ever be made directly on the main branch, which doesn't allow the tooling to create needed redlines. Instead, changes (regardless of the nature of the change) shall always be made on a new branch and managed via a PR (Pull Request). Each PR is then merged to main after approval, as noted below in at the various stages.
-
PRs should have at least (1) approver that is not the person requesting the PR. This can be the DG chair, TC chair, commentor, or secondary editor, depending on nature of the PR. For instance, on ballot state change PRs, this should be the DG or TC chair, and for publication state PRs, the TC chairs. See for more details.
- +Publishing the draft release attaches zip packages to the release details page:
+pub-rl.html) and the most-recent-release redline (release-rl.html). See for redline details and reference-base selection.See https://github.com/SMPTE/st428-24-private/releases/tag/20241101-dp, where https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/27c-st-428-24-dp-2024-12-06-pub.zip (ballot zip) and https://github.com/SMPTE/st428-24-private/releases/download/20241101-dp/20241101-dp.zip (publish zip) are available.
- The below list shows a sample workflow which would be the steps for an Engineering Document going through an initial draft or revision and the balloting process. -
- -Editors and Chairs should be aware of the general guidelines provided in the . -
-main called 2023-initial-draft (where "2023" is the current year).pubState () and pubStage () of the main prose element in the 2023-initial-draft branch are set to
- draft and WD, respectively.2023 Initial Draft from the 2023-initial-draft branch on GitHub. 2020115-pubmain called 2023-revision (where "2023" is the current year).pubState () and pubStage () of the main prose element in the 2023-initial-draft branch are set to
- draft and WD, respectively..smpte-build.json is updated in 2023-revision branch to last release tag
- 2020115-pub (see ) 2023 Revision from the 2023-revision branch on GitHub. The tooling with create a redline against the most recent edition of the document.<meta itemprop="pubState" content="pub" />, <meta itemprop="pubStage" content="WD" /> and <meta itemprop="pubDateTime" content="2023-04-15" /> (assumed date of completion).main.main named 20230415-wd with a tag of the same name.main called 20230415-cd1.20230415-cd1 branch to <meta itemprop="pubState" content="draft" /> and <meta itemprop="pubStage" content="CD" />..smpte-build.json is updated in 20230415-cd1 branch to 20230415-wd tag 20230415 CD1 from the 20230415-cd1 branch on GitHub.<meta itemprop="pubDateTime" content="2023-05-15" /> (assumed date of completion).<meta itemprop="pubState" content="pub" />
- pubDateTime remains unchanged from Workflow Step (5). main.main named 20230415-cd1 (or 20230515-cd1 if Workflow Step 7 was used) with a tag of the same name.main with required redlines is sent to the TC for FCD ballot. Skip to Workflow Step (9)main are used for the PCD. After PCD period ends, go back to Workflow Step (6). See for iterative CD naming. main called 2023-revision-fcd-comment-res.2023-revision-fcd-comment-res branch to <meta itemprop="pubState" content="draft" /> and <meta itemprop="pubStage" content="FCD" />..smpte-build.json is updated in 2023-revision-fcd-comment-res branch to 20230415-cd1 (or 20230515-cd1) tag 2023-revision-fcd-comment-res as needed to resolve comments. The tooling creates redline for review against the last edition (release 20230415-cd1 or 20230515-cd1).<meta itemprop="pubState" content="pub" /> and <meta itemprop="pubDateTime" content="2023-07-15" /> (assumed date of completion).main.main named 20230715-fcd with a tag of the same name.main is sent to the TC for pre-DP review.main called 20230415-dp (or 20230715-dp if Workflow Step 5 was used or 20230715-dp if Workflow Step 10 was used).20230415-dp branch to <meta itemprop="pubStage" content="DP" />.smpte-build.json is updated in 20230415-dp branch to 20230415-cd1 tag (or 20230515-cd1)20230415-cd1 or 20230515-cd1 or 20230715-fcd).main.main named 20230415-dp (or 20230515-dp or 20230715-dp) with a tag of the same name.main is sent to DoS for ST audit.main called 20230415-pub (or 20230515-pub or 20230715-pub).20230415-pub branch to <meta itemprop="pubStage" content="pub" />.smpte-build.json is updated in 20230415-pub branch to 2020115-pub tag 20230415-pubmain.main named 20230415-pub (or 20230515-pub or 20230715-pub) with a tag of the same name.20230415-pub.zip (or 20230515-pub.zip or 20230715-pub.zip) generated in the release to use in the https://github.com/SMPTE/document-library.
-