Skip to content

Release 2 — requirements tracker #591

Open
4 of 15 issues completed
Open

Description

@filvecchiato

What is still missing for Release 2, split by workstream. Each category is a sub-issue
stating what has to be true; the issues that serve it are its own sub-issues and carry its
label.

How membership works

An issue is a sub-issue of exactly one category — its main home. Labels are not restricted
that way, so an issue serving more than one category carries every label that applies; that
is how cross-category work is tracked.

Categories state what has to be true and are not amended to match what shipped. Current
state, staging and open questions live in the issues that serve them.

Not in Release 2

The post-W3F account and identity RFCs; Jollity's behaviour once a product is reached, as
opposed to reaching it; Chat Extension v2, since the chat category needs the surface that
exists; and runtime-aware App executables.

Activity

  1. added
    EpicScope of work per functionality per release, progress lives in sub-issues
    on Sep 3, 2026
  2. 11 remaining items

  3. added
    EpicScope of work per functionality per release, progress lives in sub-issues
    on Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

EpicScope of work per functionality per release, progress lives in sub-issues

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions