[wp-trac] [WordPress Trac] #56362: Remove Link/Bookmark API form Core: Phase 2

[WordPress Trac]

#56362: Remove Link/Bookmark API form Core: Phase 2
-------------------------+-----------------------
 Reporter:  desrosj      |       Owner:  desrosj
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.2
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------
Changes (by desrosj):

 * keywords:   => needs-patch
 * milestone:  6.1 => 6.2


Comment:

 Replying to [comment:5 jrf]:
 > I don't remember ever seeing a notice about turning on the plugin in the
 dashboard either, so I suspect there are a lot more sites out there which
 still use the API and have no clue that they were expected to turn on a
 plugin.
 >
 > As site-owners often skip a number of WP releases when updating, I think
 only allowing one major with the dashboard notice is cutting things a
 little too fine.
 >
 > That is, of course, unless the dashboard notification telling people to
 turn on the plugin is backported all the way back to WP 3.7.

 I was thinking of going the opposite way. Instead of backporting the
 notice, the first major release after moving the necessary code to the
 plugin would include an admin notice that displays when sites appear to be
 using the API without the plugin instructing them to install the plugin
 because the API will be removed in a future release. Paired with
 `__deprecated_function()` notices, this would hopefully be enough
 feedback/heads up.

 Totally open to waiting more than 1 release if that's the consensus. But I
 think the approach I described above could allow for 1 or 2 major
 releases.

 Time is running out on 6.1, though, so I'm going to focus on this next
 release.

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