Scheduling: publish binaries and an installer, or keep the README honest

Open
#1,240 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python, rust
Domain
build-system, documentation, release, testing

Research direction

Start with release/scripts/release_candidate.py and the _relay_v2_payload_inventory handling, then read release/scripts/test_registry_release.py to understand the existing inventory assertions. Trace how sibling runtime binaries and installers are built, checksummed, and uploaded. Done means Scheduling has the matching release entries and tests, and README.md documents the installer and SCHEDULING_INSTALL_DIR again.

Written by the indexing model from the issue text.

Description

area:release criticality:p2 triage:needs-implementation

What

Registry Scheduling ships a container image but no released binary and no
installer, while crates/registry-scheduling/install.sh exists in the tree
and the other runtimes all publish one.

release/scripts/release_candidate.py gates each product's payloads behind a
minimum version, for example BREG_RELEASE_MINIMUM_VERSION and
CASEWORK_RELEASE_MINIMUM_VERSION, each adding three platform binaries plus
the versioned and unversioned installer. Scheduling has no such block. The
container image roster is wired (SCHEDULING_RUNTIME_IMAGE_NAMES), so the
image half of the story is already true.

Because _relay_v2_payload_inventory is compared for exact equality, adding
the assets to a release manifest without extending the inventory first is
refused as unexpected payloads.

Why it is filed rather than fixed

The README in #1092 advertised scheduling-install.sh and a
SCHEDULING_INSTALL_DIR override that no release would produce. That PR now
states what is true today instead. Wiring the artifacts through the release
pipeline touches release provenance, which is security-sensitive and wants its
own reviewed change rather than being folded into a 173-file feature PR.

Done when

  • release_candidate.py carries a scheduling minimum-version block adding the
    platform binaries and both installer names.
  • The release workflow builds, checksums, and uploads them on the same terms as
    the sibling runtimes.
  • README.md names the installer again, and SCHEDULING_INSTALL_DIR returns to
    the override list.
  • release/scripts/test_registry_release.py covers the new inventory entries.
Dominant language
Rust
Stars
2
Forks
0
Avg merge
3h 45m
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.