Skip to content

eMule Broadband Edition 0.7.3 RC Release Dashboard

This is the current release dashboard for RC target emulebb-v0.7.3-rc.1. Use it for status, release-source truth, and the open RC task list.

Current Status

  • Status: Final proof in progress.
  • Proof status: release proof resumed by operator direction on 2026-05-17. Live proof, package refresh, and evidence recording are active; Git tagging still requires a later separate operator instruction.
  • Release freeze: active. No new feature, refactor, UI polish, warning-debt, or roadmap work enters RC 0.7.3; only direct release-gate blockers may be fixed before the tag.
  • Current hold: none for release proof. Continue one gate at a time and stop before Git tagging until the operator gives the separate RC tag instruction.
  • Release source: selected reviewed main commit in EMULE_WORKSPACE_ROOT\workspaces\workspace\app\emulebb-main.
  • Tag target: emulebb-v0.7.3-rc.1 on the selected reviewed main commit after fresh proof passes and the operator gives a separate tagging instruction.
  • Stock/community comparison baseline: baseline/community-0.72a.
  • Release stabilization branch: release/0.7.3 once the operator starts the RC branch.
  • Package publication: held until all RC-blocking item IDs below are closed or explicitly accepted, final proof passes, and fresh packages are generated.

Release Identity

  • Public product name: eMule broadband edition
  • Compact app/mod/API name: eMuleBB
  • GitHub organization and URL slug: emulebb
  • Tag: emulebb-v0.7.3-rc.1
  • Assets:
  • emulebb-0.7.3-rc.1-x64.zip
  • emulebb-0.7.3-rc.1-x64.sbom.spdx.json
  • emulebb-0.7.3-rc.1-arm64.zip
  • emulebb-0.7.3-rc.1-arm64.sbom.spdx.json
  • optional controller asset: emulebb-0.7.3-rc.1-amutorrent-x64.zip
  • optional controller SBOM: emulebb-0.7.3-rc.1-amutorrent-x64.sbom.spdx.json

Active Control Docs

Historical gate evidence and superseded cluster plans live under docs\history\release-0.7.3. Release audit provenance lives under docs\history\release-0.7.3\audits.

Open RC Tasks

ID Priority Area Required outcome
CI-035 Major Final proof Current-head RC proof passes and fresh x64/ARM64 core package hashes plus optional aMuTorrent x64 hash are recorded.

Remaining Release Backlog

The RC backlog is narrowed to CI-035. CI-038 is Done with a current-head ui-resource-depth pass covering all 43 release languages. Remaining work is final certification proof, fresh x64/ARM64 core package regeneration, optional aMuTorrent x64 package regeneration, package SBOM generation, hash recording, clean-worktree confirmation, and the later operator-controlled tag instruction.

All other active FEAT, REF, warning-debt, cleanup, and polish items are post-0.7.3 by default. A non-blocking item may enter the RC only if a current release gate exposes a direct blocker and the item doc records that promotion explicitly.

FEAT-056 remains post-0.7.3 automation and evidence UX work. It is not an RC tag blocker unless a later item promotes a specific slice.

Accepted non-blockers for RC 0.7.3:

  • CI-034: package-release now rejects dirty provenance inputs and records selected main source/build/test/tooling commits in package manifests.
  • CI-037: the expanded weak-path live profile is supported and has passed with 100/100 required REST live download triggers; cite it as evidence unless a later release-candidate change invalidates it.
  • BUG-102: aMuTorrent browser smoke now uses generated harness ports with isolated state and passed on current main.
  • BUG-111: release, update, and help URLs now use the policy-owned emulebb namespace.
  • BUG-112: legacy WebServer/qBit-compatible session-token hardening is Wont-Fix for this beta.
  • FEAT-057: qBittorrent-style download shortcuts and batch menu actions landed as user-facing polish; it does not change the final proof/package/tag gates.
  • FEAT-058: final closeout copy/audit polish aligned release-facing docs with the RC 0.7.3 source rule; it resets the candidate head but does not replace fresh proof or package hashes.
  • FEAT-059: Display preferences now keep Always show tray icon adjacent to Minimize to system tray; it resets the candidate head but does not replace fresh proof or package hashes.
  • FEAT-060: preference INI keys are now covered by a machine-readable inventory and REST mutable preference metadata is centralized; it resets the candidate heads but does not replace fresh proof or package hashes.
  • FEAT-061: a strong section-qualified preference schema now validates storage uniqueness, REST bindings, and Preferences UI source bindings; it resets the build-tests/tooling candidate heads but does not replace fresh proof or package hashes.
  • FEAT-071: remote filename intake now repairs conservative Western mojibake and bounded HTML/XML entities before existing filename cleanup; it resets the app/build-tests/tooling candidate heads but does not replace fresh proof or package hashes.
  • REF-034: Crypto++ 8.9 dependency refresh is deferred post-0.7.3.
  • IP-filter HTTP update transport from BETA-READINESS-SECURITY-2026-05-11 is accepted as not release scope.

Ship Rule

RC 0.7.3-rc.1 can be tagged only when:

  • every row in Open RC Tasks is Done or explicitly accepted in its item doc;
  • RELEASE-0.7.3-CHECKLIST records fresh command, artifact, commit, and package evidence;
  • no active workspace repo has unrelated uncommitted changes; and
  • the operator gives a separate tagging instruction.

The accepted FEAT-058, FEAT-059, FEAT-060, FEAT-061, and FEAT-071 closeout hardening changed release-facing documentation, app UI, app REST metadata, build-test guardrails, and remote filename intake after the previous prep audit. Final proof must target the pushed heads that exist after this polish and hardening lands.