Cut the first release. This is the issue that closes the plan, and it is a
checklist rather than a piece of work, which is the point: if anything on it is not
already true, the milestone it belongs to was not finished.
Before the tag. Every earlier milestone closed. The required set on the default
branch matches the parity document. The licence question answered and the licence
file present, since publishing a binary under no licence gives the person who
downloads it nothing. The default suite green with no display and no elevated
privileges. At least one experiment in a terminal state with a real answer, because
a tool for checking experiment records that ships having never seen one is untested
in the only way that matters.
At the tag. The release workflow runs and produces the artefacts. The smoke job
downloads and runs them. The release notes say what this is, what it is for, and
what it is not, and the last of those is the most important sentence in them.
After. Read the first run as a stranger would. If any output needs explaining
beyond the operator guide, that is a defect and it gets an issue rather than a
paragraph of guidance somewhere.
The release notes state the scope plainly. This is a tool for reading and checking
this board's own records. It is not something a media server user is asked to
install, it is not advertised anywhere, and nothing on any other board depends on
it. Those three exclusions are what this board was opened with, and saying them at
the moment of the first release is the point where they are most likely to start
quietly eroding.
Done when a tagged release exists carrying the binaries, checksums, bill of
materials, notices, notice, licence and privacy document, the smoke job has passed
against it, and the release notes carry the three exclusions above.
Cut the first release. This is the issue that closes the plan, and it is a
checklist rather than a piece of work, which is the point: if anything on it is not
already true, the milestone it belongs to was not finished.
Before the tag. Every earlier milestone closed. The required set on the default
branch matches the parity document. The licence question answered and the licence
file present, since publishing a binary under no licence gives the person who
downloads it nothing. The default suite green with no display and no elevated
privileges. At least one experiment in a terminal state with a real answer, because
a tool for checking experiment records that ships having never seen one is untested
in the only way that matters.
At the tag. The release workflow runs and produces the artefacts. The smoke job
downloads and runs them. The release notes say what this is, what it is for, and
what it is not, and the last of those is the most important sentence in them.
After. Read the first run as a stranger would. If any output needs explaining
beyond the operator guide, that is a defect and it gets an issue rather than a
paragraph of guidance somewhere.
The release notes state the scope plainly. This is a tool for reading and checking
this board's own records. It is not something a media server user is asked to
install, it is not advertised anywhere, and nothing on any other board depends on
it. Those three exclusions are what this board was opened with, and saying them at
the moment of the first release is the point where they are most likely to start
quietly eroding.
Done when a tagged release exists carrying the binaries, checksums, bill of
materials, notices, notice, licence and privacy document, the smoke job has passed
against it, and the release notes carry the three exclusions above.