Skip to content

Milestones

List view

  • One downloadable file, one verb, nothing installed. An operator can check out this repository, run the release against it, and read what it examined.

    No due date
    1/6 issues closed
  • An experiment that worked has to reach a product board or the good results stay here. This milestone builds that path and the record it leaves on both sides.

    No due date
    4/4 issues closed
  • Personal data never leaves the host unless the operator deliberately federates, the tooling is built so that this is true rather than promised, and the documentation says it plainly.

    No due date
    2/5 issues closed
  • The merge gate of Flowfin/jellyfin-plugin-sso is the target. Every check it requires is kept, renamed or dropped here, with one line of reasoning for each deviation, and the surviving set is what the default branch requires.

    No due date
    13/16 issues closed
  • Every test in the default run completes with no display and no elevation. The requirement itself is recorded with the decisions, because the test harness depends on it before this milestone starts; what this milestone builds is the machinery that refuses a violation and the separate harness for work that genuinely needs hardware, which says so in its name and prints why it skipped.

    No due date
    5/5 issues closed
  • The rule that keeps this from becoming a graveyard, made refusable. An experiment states its question before it starts and its answer when it stops, the answer may be no, and a machine refuses the records that do not.

    No due date
    24/25 issues closed
  • Language, toolchain, layout, community health files and a test harness. At the end of this milestone the repository builds, tests and reports under check names that are written down.

    No due date
    21/23 issues closed
  • The decisions this repository is built on, each written down with its reasons and its rejected alternatives before anything depends on it. Nothing in the later milestones starts until the decision it rests on is in the tree, and that ordering is recorded on the issues themselves as blocking relationships rather than only in this sentence, so an issue whose decision is still open shows as blocked instead of looking startable.

    No due date
    12/14 issues closed