[META] Remove all @deprecated functions marked "remove before 8.0"

Should we be adding a Change record to the tasks that remove the deprecated function? Or maybe have one Change record for all of them?

Added child issue #2299253: Remove language_access_language_edit_or_delete function.

Added mail.inc deprecated functions.

Adding #2383727: Remove form_options_flatten() as it is deprecated

Added beta evaluation.

Overlap here: #2093143: [meta] Remove calls to @deprecated and "backwards compatibility" procedural functions from core

This looks really close, to the point where I think if there are one or two left at the end, we should consider updating the documentation if they don't happen before release candidate. However we can still commit these right up until the first release candidate. Untagging.

#2549041: Remove deprecated _drupal_set_preferred_header_name() removes _drupal_set_preferred_header_name().

A bit of an API snag here: #2555069: Remove invocation of hook_html_head_alter()

Should really be critical, but I don't run the world.

I can't think of a reason why we would not ship D8 if this wasn't done. However, it does definitely need to get done before RC if we're going to do it, so tagging.

Tweak the grep because vendor moved to root.

I guess we'll likely need to move this to 8.1.x since RC is out. They are still marked deprecated the deadline for removing them has past.

The biggest hunks seems to be db_ functions file functions.

We're not allowed to remove functions in D8.1 unless we really, really need to, so there's basically no more removal of functions to be done in the short to medium term.

...Thus illustrating a major flaw in a criticals-based release process.

Anyway, yes, here's what remains:

UrlGeneratorInterface::getPathFromRoute() #2307061: UrlGeneratorInterface::getPathFromRoute() is marked deprecated but will not be removed, so update the docs

Url::getInternalPath() #2367753: \Drupal\Core\Url::getInternalPath() cannot be deprecated

These deprecations should occur, and those methods should be removed from core, if they really are deprecated.

If they're not deprecated, then a maintainer should say so.

Setting RTBC in hopes of getting maintainer input.

Not appropriate usage of priority or status.

Hah, just saw webchick's post and came back to change this.

https://groups.drupal.org/node/486388

Since this is a meta and different removals of different deprecated functions have different impact, let's instead tag any outstanding child issues for triage individually.

See: #2205685: Review @deprecated functions that are not marked "will be removed before Drupl 8.0"

I think this is done? ... all the child issues are complete

No activity since 2015

All I found were these:

git grep -e '@deprecated.*before Drupal 8'
core/modules/system/src/Tests/Entity/EntityUnitTestBase.php: * @deprecated in Drupal 8.1.x, will be removed before Drupal 8.2.x. Use
core/tests/Drupal/FunctionalJavascriptTests/JavascriptTestBase.php:   * @deprecated in Drupal 8.1.x, will be removed before Drupal 8.3.x. Use
core/tests/Drupal/FunctionalJavascriptTests/JavascriptTestBase.php:   * @deprecated in Drupal 8.1.x, will be removed before Drupal 8.3.x. Use
core/tests/Drupal/KernelTests/KernelTestBase.php:   * @deprecated in Drupal 8.0.x, will be removed before Drupal 8.2.0.

cilefen++ That git grep is a really useful command

Just for the record

It looks like you did that on the 8.4.x branch .. or at least the results are the same.

I don't think it is worth promoting a fixed issue 8.3.x upto 8.4.x

cleanup on aisle 8.4