@@ -99,10 +99,10 @@ been filed specifically for the agenda, and whether any items need attention.
9999| ` lifecycle/blocked-on-author ` | ` S-waiting-on-author ` |
100100| ` lifecycle/confirmed ` | ` S-confirmed ` |
101101| ` lifecycle/duplicate ` | (1) |
102- | ` lifecycle/fixed ` | ` S-fixed ` |
102+ | ` lifecycle/fixed ` | (2) |
103103| ` lifecycle/needs-review ` | ` S-needs-triage ` |
104- | ` lifecycle/not-a-bug ` | (2 ) |
105- | ` lifecycle/wont-fix ` | (3 ) |
104+ | ` lifecycle/not-a-bug ` | (3 ) |
105+ | ` lifecycle/wont-fix ` | (1 ) |
106106| ` question ` | ` C-question ` |
107107| ` ready-for-review ` | ` S-waiting-on-review ` |
108108| ` regen-goldens ` | ` S-needs-golden-regen ` |
@@ -113,9 +113,9 @@ been filed specifically for the agenda, and whether any items need attention.
113113| ` size/xl ` | ` E-hard ` |
114114| ` size/xs ` | ` E-easy ` |
115115
116- - 1: Link issue and close as not planned
117- - 2: Explain the finding and close as not planned
118- - 3: Close as not planned
116+ 1 . Link issue and close as " not planned"
117+ 2 . Close the issue as "completed"
118+ 3 . Explain the finding and close as " not planned"
119119
120120### New labels
121121
@@ -180,4 +180,16 @@ up for agendas to discuss as part of triage.
180180### Why is “participation” labeled with “E-”
181181
182182“Priority” is labeled “P-”, meaning participation needs a different prefix. Rust
183- uses “E-” which seems as good as any other.
183+ uses “E-” for this, which seems as good as any other choice.
184+
185+ ### Why rename "lifecycle" to "status"
186+
187+ The term "lifecycle" implies that it can only represent one state at any given
188+ time, e.g. * "Which state in the lifecycle are we on?"* . The term "status" does
189+ not imply that same restriction, and any item can have one or more status
190+ modifiers at any given time.
191+
192+ This is nice, because it allows us to tag an item as ` S-waiting-on-review ` ,
193+ while also being ` S-nominated ` for the next community meeting. In comparison:
194+ "nominated for the next meeting" does not feel like it would naturally be part
195+ of any "lifecycle".
0 commit comments