Product polish severity bar #43

New issue

Closed

opened 2026-08-03 22:42:31 +00:00 by TheAnachronism · 1 comment

TheAnachronism commented

2026-08-03 22:42:31 +00:00

Owner

Part of #41

Question

What severity levels and exit rules decide whether a product rough edge or bug blocks 1.0 beta (sideload-to-friends), versus ship-with-known-issue?

Part of #41 ## Question What severity levels and exit rules decide whether a product rough edge or bug blocks 1.0 beta (sideload-to-friends), versus ship-with-known-issue?

TheAnachronism added the

wayfinder:grilling

label

2026-08-03 22:42:57 +00:00

TheAnachronism referenced this issue

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

Beta-blocking known issues #45

TheAnachronism self-assigned this

2026-08-04 00:30:12 +00:00

TheAnachronism commented

2026-08-04 00:32:53 +00:00

Author

Owner

Resolution

Three exit buckets for product rough edges / bugs against sideload-to-friends 1.0 beta:

Blocker — must fix before beta
Document — ship with known-issue (listed in readiness known-issues inventory)
Ignore — omit from friends-facing known-issues for this release

Blocker

Breaks the core reading loop, or safety. Core-loop breakage stays Blocker even when a reliable workaround exists.

Core reading loop: Sign-in / Account switch → List hub + Drawer tree selection → open Reader → mark read / star / mark unread → open original; plus Mark-read mode correctness, Unread filter behavior, and systematically wrong Unread counts.

Safety: data/credential integrity failure; wrong mark/star at scale; destructive Account wipe without clear user action; unrecoverable bricking until clear-data. (Friends privacy wording is packaging-bar work, not this taxonomy.)

Document

Likely in normal use and surprising (friend may think the app is broken or blame themselves); still workable.

Ignore

Cosmetic, rare, or already an MVP non-goal.

Explicitly not Blockers by default

Common Reader media polish, excerpts/thumbnails, and general “embarrassing” UI — unless they make the core loop unusable.

Apply this bar to the seed inventory in Beta-blocking known issues (after Seed known-issues inventory).

## Resolution **Three exit buckets** for product rough edges / bugs against sideload-to-friends **1.0 beta**: 1. **Blocker** — must fix before beta 2. **Document** — ship with known-issue (listed in readiness known-issues inventory) 3. **Ignore** — omit from friends-facing known-issues for this release ### Blocker Breaks the **core reading loop**, or **safety**. Core-loop breakage stays Blocker even when a reliable workaround exists. **Core reading loop:** Sign-in / Account switch → List hub + Drawer tree selection → open Reader → mark read / star / mark unread → open original; **plus** Mark-read mode correctness, Unread filter behavior, and systematically wrong Unread counts. **Safety:** data/credential integrity failure; wrong mark/star at scale; destructive Account wipe without clear user action; unrecoverable bricking until clear-data. (Friends privacy wording is packaging-bar work, not this taxonomy.) ### Document Likely in normal use **and** surprising (friend may think the app is broken or blame themselves); still workable. ### Ignore Cosmetic, rare, or already an MVP non-goal. ### Explicitly not Blockers by default Common Reader media polish, excerpts/thumbnails, and general “embarrassing” UI — unless they make the core loop unusable. Apply this bar to the seed inventory in [Beta-blocking known issues](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/45) (after [Seed known-issues inventory](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/44)).

TheAnachronism closed this issue

2026-08-04 00:32:53 +00:00

TheAnachronism referenced this issue

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

1.0 beta release readiness #41

TheAnachronism referenced this issue

2026-08-04 00:45:03 +00:00

Beta-blocking known issues #45