[BUILD DELIVERY REQUEST] test #2378

What is the name of this build?

26Q3_B22.2

Which revision should this build be based on?

1.0.1

IF THIS IS A PATCH ON AN EXISTING RELEASE, which changes should be included?

tbd

Release Candidate?

• Is this a release candidate (NOT to be published to PyPI)?

Optionally, include release notes for the GitHub release.

No response

Release Procedure

freeze and tag code

• Release new versions of STScI-developed dependencies (stcal, stpipe, etc.) if they introduce new bugfixes or features required by the pipeline.
• Ensure pipeline dependencies in pyproject.toml are NOT floating on main (e.g. stcal@git+https://github.com/spacetelescope/stcal.git@main), and instead use PyPI releases (e.g. stcal>=1.19,<2) instead (or, at the very least, point to a specific commit hash). The lower pin does not necessarily need to be the latest release, but rather is based on features / fixes required by the pipeline code.
• Determine the new <VERSION>; if breaking changes are present (changes/*.breaking.rst) increment the major version (1.1.3 -> 2.0.0), else if new features are present increment the minor version (1.1.3 -> 1.2.0), else if only bugfixes are present increment the micro version (1.1.3 -> 1.1.4). If this is a release candidate (indicated above), add an rc1, or rc2, etc. to the end of the version.
• Switch to the release branch corresponding to the minor version, with the micro release as x (1.1.3 -> release/1.1.x).
• IF THIS IS A PATCH ON AN EXISTING RELEASE, duplicate the desired changes (indicated above), onto the desired base revision (indicated above).
• Run towncrier build --version <VERSION> to consume fragments in changes/ and add an entry to CHANGES.rst.
• Tag the head of the release branch with <VERSION>; if this is NOT a patch release, also increment main to point to the new tag.

run "canonical" regression test for metrics dashboard

• On Artifactory (https://bytesalad.stsci.edu), copy a truth file directory to roman-pipeline/build/<BUILDNAME> in order to freeze them. IF THIS IS A PATCH RELEASE it will be the previous build directory roman-pipeline/build/<PREVIOUSBUILDNAME> -> roman-pipeline/build/<BUILDNAME>; otherwise simply copy roman-pipeline/dev -> roman-pipeline/build/<BUILDNAME>.
• Run a regression test with the following parameters, and note the run number:
  • using the <VERSION> tag you just made
  • "Artifactory environment" pointing to the truth file directory you just copied
  • "INT build directory" as <VERSION>
• Okify any failures for this regression test run with okify_regtests roman <RUN_NUMBER>.

publish release and deliver frozen environment

• IF NOT A RELEASE CANDIDATE (indicated above), publish a GitHub release for the new version at the tag you just made, using the release notes provided above.
• Write a stasis INI delivery configuration at a publicly accessible URL, e.g. /eng/ssb/websites/ssbpublic/zburnett/ROMANDP-<VERSION>-1.ini, pointing to romancal[sdp]=<VERSION>.
• Run stasis at https://github.com/spacetelescope/datapipeline-workflows/actions/workflows/stasis_public.yml pointing to the INI delivery configuration.