Files
chenlin d5e9004f6c
Checks / Layout, translation and Colab checks (push) Has been cancelled
Checks / Ruff (push) Has been cancelled
Checks / Framework tests (native backend, CPU) (push) Has been cancelled
Checks / Portable Rust controller (push) Has been cancelled
docs: add AI agent workflow guide and clean up residual single-robot references
2026-11-05 11:52:07 +08:00

1.6 KiB

Public release preparation

The project name is MJRL Robotics Platform. The Python distribution is mjrl-lab, its import is mjrl, and shared configuration keys use MJRL_*. Use the selected, verified publication remote for release links and clone instructions.

Review the release snapshot

  • Use a reviewed tracked-file snapshot. Preserve existing source history in its repository and publish only the intended branches and tags.
  • Verify redistribution rights for retained fixtures, model assets, policy weights, and generated artifacts. Review LICENSE, NOTICE, and third-party notices. The legacy Rockchip runtime has separate provenance and terms described in its runtime notes.
  • Inspect tracked configuration, generated packages, and archives for private content. Shared option keys are documented in .env.example. Keep .env and .env.local out of the snapshot.
  • Choose the commit identity, confirm the target remote and branch, and review changes already present there before publishing.
  • Keep release downloads and provenance tied to actual artifacts. Record source revisions and checksums. Document extra download steps for assets stored outside the repository.

Verify and document

Run the repository checks and targeted native smoke tests for the shipped features. Record which backends and runtimes were exercised. Keep observed simulation outcomes and hardware claims separate.

Set repository metadata, default branch and branch protection to match the published project and its active checks. Release notes should describe the tested artifact and supported runtime.