[wp-meta] [Making WordPress.org] #6283: Workflow keywords for release docs

Making WordPress.org noreply at wordpress.org
Wed Apr 20 00:59:33 UTC 2022

#6283: Workflow keywords for release docs
 Reporter:  milana_cap       |       Owner:  (none)
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:
 Keywords:                   |

Comment (by dd32):

 Replying to [comment:5 milana_cap]:
 > `needs-docs` and `needs-user-docs` are good enough


 > but also adding something for field guide would be very helpful. `needs-
 field-guide` might be misleading as it could sound like a very big feature
 that needs the whole field guide.

 To be honest, I didn't even know what a Field Guide was until this
 Looking at the previous fieldguides, it seems to be that fieldguides are a
 collection of Dev Notes, but Dev Notes that have been deemed to be
 important enough to highlight in an end-of-cycle post? ie. Some dev notes
 are deemed to not be as important to be included?

 Looking at the existing tickets, it doesn't look like this has been
 tracked in Trac at all? (ie. not through a custom keyword).

 I'm not sure `needs-field-guide` makes sense here, as you'd not be
 flagging things as `has-field-guide` afterwards, but perhaps `add-to-
 field-guide` as you've said makes sense.

 I've updated https://core.trac.wordpress.org/report/36 for the `needs-
 codex` change.

Ticket URL: <https://meta.trac.wordpress.org/ticket/6283#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list