Determine the <release identifier>
for the version of the standard you are about to publish.
(See ReleaseIdentifier for how these are to be constructed).
Update SQLParts.xml
for the documents you are intending to publish.
If the documents are not the final texts submitted to ISO/CS i.e. not one of the docStages: ISO/IEC, ISO/IEC PRF, COR, ISO/IEC TR, ISO/IEC TR PRF, or AMD then the value of the output="xxx" attribute of each
element must be the <release identifier>
. If the documents are the final texts submitted to ISO/CS then then the value of the output="xxx" attribute of eachelement must be:
- If the documents are parts of the 9075 standard then the value of the "Expected filenames" column of the Filenames conventions table in the "Support for the use of inter-document links in ISO/IEC 9075" Annex of SQL/Framework omitting the ".pdf". E.g., ISO_IEC_9075-11(E)_Schemata
- Otherwise, the concatenation of "ISO_IEC_",
standard-number
, "-",standard-part
, "(E)_", a short name for the standard or part. Note: if the standard is undivided the "-" andstandard-part
" are omitted. E.g., ISO_IEC_39075(E)_GQL
Rebuild all parts for publication.
Make all required changes, ensure that everything builds correctly (make all
) and commit your
changes.
Rebuild for sanity (make clean && make all
).
Manually verify that all generated PDFs are correct.
Stage the files (make stage<standard-number>
).
Copy the staged files to the appropriate ISO directory:
Pointer file PDFs to the appropriate subdirectory of the
01 Meetings-numbered documents
directory.The standard (part) PDFs to the appropriate subdirectory of the
02 Progression_Documents
directory.The zip file to the
Stable_Sources
subdirectory of the09 Build_Environment
directory.
Note: If you are responsible for maintaining the ANSI copies then you should also copy the (ANSI) pointer file PDFs and the standard (part) PDFs to the appropriate ANSI directories.
Consider placing a tag (See 'Additional tags' below).
If the documents are the subject of a CD, DIS, FDIS ballot or are the final texts submitted to ISOCS as the IS.
Copy all relevant standard (part) PDFs to the
archive/
subdirectory in git.
If the the documents are the final texts submitted to ISO/CS:
Copy all relevant standard (part) xml file (e.g.
sql-foundation.xml
) to thepublished/
subdirectory in git.
Add all the new untracked files in archive/
and published/
to git.
Commit using the message Release of <release identifier>
Tag the release with the <release identifier>
(see below)
Push commits to the remote repository, e.g. using git push origin
Additional tags may be used for the convenience of the editors.
These should be prefixed with one of the following:
The mark of the family of the standard in lowercase and with spaces replaced by dashes and followed by a dash that is followed by a descriptive name for the tagged commit
before-<place>-<yyyy>-<mm>
to tag the state of the repository before a meeting of the editor's
at <place>
in <yyyy>
(this may include WG3 meetings)
after-<place>-<yyyy>-<mm>
to tag the state of the repository after a meeting of the editor's
at <place>
in <yyyy>
(this may include WG3 meetings)
Using the command line: git tag '<release identifier>'
git push origin <release identifier>
Go to the Repository menu and choose "Visualize master's history" (Where master is the name of the branch)
This will show a list of all commits in that branch, right click on a commit and choose "Create Tag"
Use <release identifier>
as the name of the tag
Push the tag. Remember to set the check-box to also push the tag.
This file: Copyright © 2021 Editors of ISO/IEC JTC 1/SC 32/WG 3: Jim Melton, Stephen Cannan, Jörn Bartels, Stefan Plantikow