microsoft / microsoft/fluentui

ONB-05 — Read & annotate the v9 Stable release checklist

Open Beginner friendly
#36,146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Animation Fluent UI react-components (v9) Motion UXE backlog Type: Feature
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Description: Read through the v9 Stable release checklist (docs/react-v9/contributing/stable-release-checklist.md) plus related v9 promotion guidance. Produce annotations focused on motion-specific implications: which checklist gates will be straightforward for motion components, which need adapted patterns (VR tests, isConformant, bundle-size, perf), and which surface implicit motion-specific concerns. Annotations seed PROM-INFRA-09 (motion-specific addendum) and inform CHOR-01 Beta exit criteria.

Why it matters: The UXE drives Group 6 (Stable promotion readiness) in M3. They need baseline fluency in what "Stable" actually means for a v9 package before that work begins. Reading the checklist also surfaces the early questions PROM-INFRA-09 codifies.

  • Difficulty: Easy
  • Dependencies: ONB-01
  • Sequencing: M1 W2
  • Pairing: Async; questions raised in the W2 debrief
  • Output: Annotations grouped by straightforward / needs adaptation / motion-specific gap

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read docs/react-v9/contributing/stable-release-checklist.md and the related v9 promotion guidance after completing ONB-01. Record annotations grouped as straightforward, needs adaptation, and motion-specific gap, covering the checklist gates and the noted VR tests, isConformant, bundle-size, and performance considerations. Done means the annotations are ready to seed PROM-INFRA-09 and inform CHOR-01 Beta exit criteria.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, release
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.