[wp-trac] [WordPress Trac] #26334: Disable 'Featured Plugins' if they're included in Core

[WordPress Trac]

#26334: Disable 'Featured Plugins' if they're included in Core
-----------------------------+--------------------
 Reporter:  Ipstenu          |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  3.8
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+--------------------

Comment (by Ipstenu):

 Replying to [comment:2 markoheijnen]:
 > I strongly object to have something like this in core.

 I'm curious as to why?

 If we're pushing plugins as how we develop, we have to make a way to
 graceful remove the featured plugin as it's really no longer needed. Yes,
 a perfect world has prefixes etc preventing goobering, but mistakes
 happen. Since these are 'our' plugins, a disable/deactivate of the plugin
 on a site shows we're taking care of ourselves and our beta testers :)

 (Which reminds me, Sams, I think we should have a workflow plan for
 deactivating/disabling the plugin in the repo once it's in core. A disable
 will serve updates so we can push emergency fixes for people on pre 3.8
 with MP6, for example, but no longer allow people to install it anew. That
 would help limit the oops! My bad! later on. All that has to happen for
 that is someone on the core team/plugin team emailing plugins at
 wordpress.org with a link to the plugin, asking for a disable because it's
 in core now.)

--
Ticket URL: <http://core.trac.wordpress.org/ticket/26334#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software