Release channel for beta #57

New issue

Closed

opened 2026-08-03 22:43:06 +00:00 by TheAnachronism · 1 comment

TheAnachronism commented

2026-08-03 22:43:06 +00:00

Owner

Part of #41
Blocked by: #52

Question

Should 1.0 beta keep alpha/* tags and prereleases, move to beta/*, or another channel — and how does that interact with versioning and the existing alpha-release workflow?

Part of #41 Blocked by: #52 ## Question Should 1.0 beta keep alpha/* tags and prereleases, move to beta/*, or another channel — and how does that interact with versioning and the existing alpha-release workflow?

TheAnachronism added the

wayfinder:grilling

label

2026-08-03 22:43:06 +00:00

TheAnachronism referenced this issue

2026-08-04 00:48:05 +00:00

CI quality gates for beta #47

TheAnachronism referenced this issue

2026-08-04 19:11:31 +00:00

App identity and versioning #52

TheAnachronism referenced this issue

2026-08-04 19:23:53 +00:00

Friend install and update docs #56

TheAnachronism self-assigned this

2026-08-04 19:24:52 +00:00

TheAnachronism commented

2026-08-04 19:26:37 +00:00

Author

Owner

Resolution

Release channel for sideload 1.0 beta (criteria only — implement later):

Must

Tags: beta/<semver> (e.g. beta/1.0.0). Semver portion still feeds --build-name / versionName per App identity and versioning.
Forgejo releases: mark beta/* cuts as prerelease (prerelease: true).
Workflow: retarget the existing packaging workflow from alpha/* to beta/* only (strip beta/ for versionName; stop using this workflow for new alpha/* cuts in the 1.0 beta effort).
APK asset name: tt-rss-viewer-beta-<semver>.apk.
Install docs: docs/install.md names the beta channel/assets; keep only the plain alpha→beta reinstall note from earlier locks — no ongoing alpha install path.

Not must for beta

Keeping a parallel alpha/* packaging workflow for experiments
Non-prerelease / “latest” Forgejo releases for beta cuts

Why

The readiness milestone is 1.0 beta; keeping alpha/* would mismatch the channel users see on Releases. Retargeting the one packaging workflow keeps operator surface small while preserving the locked versioning scheme (tag semver + epoch versionCode) and prerelease signaling.

## Resolution **Release channel** for sideload **1.0 beta** (criteria only — implement later): ### Must 1. **Tags:** `beta/<semver>` (e.g. `beta/1.0.0`). Semver portion still feeds `--build-name` / versionName per [App identity and versioning](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/52). 2. **Forgejo releases:** mark `beta/*` cuts as **prerelease** (`prerelease: true`). 3. **Workflow:** retarget the existing packaging workflow from `alpha/*` to **`beta/*` only** (strip `beta/` for versionName; stop using this workflow for new `alpha/*` cuts in the 1.0 beta effort). 4. **APK asset name:** `tt-rss-viewer-beta-<semver>.apk`. 5. **Install docs:** `docs/install.md` names the **beta** channel/assets; keep only the plain alpha→beta reinstall note from earlier locks — no ongoing alpha install path. ### Not must for beta - Keeping a parallel `alpha/*` packaging workflow for experiments - Non-prerelease / “latest” Forgejo releases for beta cuts ### Why The readiness milestone is **1.0 beta**; keeping `alpha/*` would mismatch the channel users see on Releases. Retargeting the one packaging workflow keeps operator surface small while preserving the locked versioning scheme (tag semver + epoch versionCode) and prerelease signaling.

TheAnachronism closed this issue

2026-08-04 19:26:38 +00:00

TheAnachronism referenced this issue

2026-08-04 19:27:26 +00:00

1.0 beta release readiness #41