[wp-meta] [Making WordPress.org] #5118: Introduce dev-note field to Trac

[Making WordPress.org]

#5118: Introduce dev-note field to Trac
----------------------------------------------------+---------------------
 Reporter:  garrett-eclipse                         |       Owner:  (none)
     Type:  enhancement                             |      Status:  new
 Priority:  normal                                  |   Milestone:
Component:  Trac                                    |  Resolution:
 Keywords:  has-patch has-screenshots dev-feedback  |
----------------------------------------------------+---------------------

Comment (by dd32):

 Replying to [comment:7 garrett-eclipse]:
 > My feeling is it's an awesome start and as people start using it we can
 iron out the wrinkles.

 My main hesitation is that if there's anything about the implementation
 (other than things we can fix with JS) then as it's Trac it'll be much
 harder to alter.


 Replying to [comment:8 davidbaumwald]:
 > This is a great idea.  FWIW, for the last couple of major releases, the
 list of dev notes has been compiled with third-party tools, like Google
 Docs/Sheets.

 I don't think this will 100% replace that flow, but it might help trigger
 people to fill in the notes during the dev cycle, making the end-of-
 release-cycle task mostly to be to pull them all together and make it flow
 together well.


 Replying to [comment:9 whyisjake]:
 > Would it make sense to have the field collapsed normally? I can imagine
 a lot of comments being dumped there.

 It's only shown if the `need-dev-note` or `has-dev-note` keywords exist
 (Or, those keywords were removed and there's still content in the field
 from previously).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5118#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org