Updated: Comment #1
Problem/Motivation
After beta we will be much stricter about removing any APIs that might be being used by contrib modules. To avoid needing to ship and maintain obsolete APIs we want to remove as many as possible before beta.
Rather than having to maintain a list of child issues on this META, we are using the @deprecated tag. You can see the list of open child issues at https://drupal.org/project/issues/search?projects=Drupal+core&status[]=O...
Proposed resolution
Each API or group of related APIs should be handled in their own sub-issue, which should be tagged @deprecated and, if suitable, Novice.
Many APIs are easy to remove, for example they may just be a wrapper around another function. Where this is the case, they should be removed immediately. A single patch can be used to resolve any remaining uses of the API and remove the API itself. Where a removal is very simple you are encouraged to combine multiple related APIs into a single patch to make the review and commit process easier.
Where an API is still being used by core code it may not be possible to remove it in time for beta, even though we plan to remove it before release. In these cases (or where you are unsure on timescales) the API must be marked @deprecated in the docblock, with an indication of when it will be removed, the issue that will remove it and what should be used instead. For example:
...
*
* @deprecated in Drupal 8.x-dev. Will be removed before Drupal 8.0-rc1
* by https://drupal.org/node/2167167. Use
* Field::fieldInfo()->getField($field_name).
*/
function field_info_field($entity_type, $field_name) {
...or if a more detailed explaination is needed, use a @see directive
...
*
* @deprecated in Drupal 8.x-dev. Will be removed before Drupal 8.0-beta1
* by https://drupal.org/node/1959574.
*
* @see https://drupal.org/node/1843212
*/
function ajax_prepare_response($page_callback_result) {
...A separate issue should be opened for the actual removal of the API.
Remaining tasks
Get this proposal signed off by core maintainers (hence why this is currently postponed).
Create or tag child issues for known deprecated APIs (see https://docs.google.com/spreadsheet/ccc?key=0AusehVccVSq2dEttQ3k5WWNYVHB... ).
Resolve all child issues.
User interface changes
N/A
API changes
A "few" removals
Follow-up from #2158871: [Policy, no patch] Clearly denote when @deprecated code is slated to be removed.
#2185015: Remove SchemaCache and CacheArray
Comments
Comment #1
ianthomas_ukComment #2
cosmicdreams commentedAlso We shouldn't be using Twig_NodeInterface anymore and use Twig_Node instead. See http://twig.sensiolabs.org/doc/deprecated.html
Comment #3
cosmicdreams commentedComment #4
cosmicdreams commentedComment #5
xjmThis is either critical, or not a beta blocker. Which? :) (Check with a core maintainer before adding the beta blocker tag.)
Also, I'm not sure entirely about the issue approach/scope as described.
Comment #6
ianthomas_ukIt was an attempt to get a decision made on the policy in this area. It hasn't worked, and it's probably easier to start again with a new issue with a different scope than edit this one.
Closing as a duplicate, because there will be other issues to solve this problem, they just haven't been opened yet.
Discussion continues in #2158871: [Policy, no patch] Clearly denote when @deprecated code is slated to be removed