[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged

[WordPress Trac]

#32101: Ability to mark plugin as unmanaged
-------------------------------------+---------------------------
 Reporter:  damonganto               |       Owner:  DrewAPicture
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  4.4
Component:  Plugins                  |     Version:  4.1.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------------

Comment (by knutsp):

 `Update` seems like a better idea as a header name. This is more
 extensible and future proof.

 In the first iteration (4.4) this value should only accept
 N/No/None/F/False meaning no updates from wp.org repo.

 Later this may have other values like Major/Minor/Security/Manual or
 whatever when new features regarding (auto) updates may be desirable and
 implemented. Both opt-in and opt-out. In any case this should hold
 information that instructs the update mechanism in core how to handle
 updates.

 I see a future where some widely used plugins may opt-in to enable pushing
 security updates regardless of auto update settings (done manually today,
 through the security team), and some plugins to opt-out of any automatic
 updates (if allowed as a future decision).

 `Private` as header has far less such future opportunities.

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