[wp-trac] [WordPress Trac] #30465: Dashboard alert if a plugin/theme was removed from WordPress repo

[WordPress Trac]

#30465: Dashboard alert if a plugin/theme was removed from WordPress repo
-----------------------------------------------+-----------------------
 Reporter:  sergej.mueller                     |       Owner:  (none)
     Type:  feature request                    |      Status:  reopened
 Priority:  normal                             |   Milestone:  6.4
Component:  Security                           |     Version:
 Severity:  normal                             |  Resolution:
 Keywords:  dev-feedback needs-patch security  |     Focuses:
-----------------------------------------------+-----------------------
Changes (by hellofromTonya):

 * keywords:  dev-feedback needs-patch early security => dev-feedback needs-
     patch security


Comment:

 I'm doing an audit of all tickets marked 6.4 `early`. What is `early`?

 [https://make.wordpress.org/core/handbook/contribute/trac/keywords/ The
 handbook explains the keyword as]:
 >This keyword should only be applied by committers. The keyword signals
 that the ticket is a priority, and should be handled early in the next
 release cycle.

 `early` means the commits need to happen during the early part of the
 Alpha cycle; else, the ticket gets bumped.

 Is this ticket an `early` candidate?

 Should it be constrained to only happen during the early part of the 6.4
 Alpha cycle, meaning it will get bumped if it isn't completed in time?

 I'm thinking no. Once the API work is done, then commits for this ticket
 could happen up to 6.4 Beta 1. Rather than risk the ticket being bumped if
 not done in the early phase, I've removed the `early` keyword. It also
 helps the 6.4 Release Squad track.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/30465#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform