Problem/Motivation

Track the steps needed to deprecate extension Telephone. See Remove a core extension and move it to a contributed project of the deprecation policy.

The removal of extension Telephone was approved in #3266465: [policy, no patch] Remove Telephone module from core.

Remaining tasks

  1. Begin finding someone to maintain the contrib version of the extension. smustgrave has volunteered
  2. Add the extension to the list of the Upcoming Deprecations. - Done
  3. Move integrations implemented by other modules to the extension.
    Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
  4. Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
  5. Create the contrib project with a stable release, before the alpha version of the major release. Follow the process in Create the contrib project with a stable release for creating the sub tree split.
  6. Deprecate the core extension. #3594202: Deprecate the Telephone module - in review
  7. Create an issue, 'Ensure that Telephone does not get special core treatment' in the packages.drupal.org issue queue to ensure that the composer namespace for the contributed project matches the core one after removal. This is to allocate the drupal/telephone Composer namespace to contrib extension rather than the core extension. - Opened https://git.drupalcode.org/project/project_composer/-/work_items/3583681
  8. Update the Deprecated and obsolete extensions

Comments

quietone created an issue. See original summary.

quietone’s picture

quietone commented
Issue summary: View changes
quietone’s picture

quietone commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented
Issue summary: View changes

Thank you for creating this! On the policy I volunteered to be the contrib maintainer so scratching that step off.

smustgrave’s picture

smustgrave commented
Issue summary: View changes

From what I can tell there is no references in any DB dumps and no templates in the themes.

There is 1 mention in a core.content_struct.html.twig for help topic, do we copy the whole thing to telephone?

Currently the namespace is owned by Dave Reid so I've reached out to him about transferring it over https://www.drupal.org/project/telephone

smustgrave’s picture

smustgrave commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented
smustgrave’s picture

smustgrave commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented
Issue summary: View changes

just got access to the namespace doing the split now.

smustgrave’s picture

smustgrave commented
Status: Active » Needs review

Believe all tasks are complete.

smustgrave’s picture

smustgrave commented
Issue summary: View changes
quietone’s picture

quietone commented
Status: Needs review » Active

Still needs step 6.

quietone’s picture

quietone commented 
$ git grep telephone | grep -v deprecation-ignore | grep -v core/modules/telephone
core/lib/Drupal/Core/Render/Element/Tel.php: * Provides a form element for entering a telephone number.
core/modules/system/tests/src/Functional/Form/FormTest.php:    $elements['telephone']['element'] = ['#title' => $this->randomMachineName(), '#type' => 'tel'];
core/modules/system/tests/src/Functional/Form/FormTest.php:    $elements['telephone']['empty_values'] = $empty_strings;
core/themes/stable9/tests/Kernel/Stable9LibraryOverrideTest.php:    'telephone/drupal.telephone-icon',

That is for the htlm5 element, so no further uses of telephone in core.

quietone’s picture

quietone commented
Issue tags: +11.5.0 release priority
quietone’s picture

quietone commented
Status: Active » Fixed
Issue tags: -11.5.0 release priority

I updated the doc page, the last step. So this is now complete.

I am removing the tag as well, so this doesn't come up in searched when making the 11.5 release notes.

I am sure this sets the record for the fastest deprecation of an extension, 3 weeks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.