Problem/Motivation

  • Some issues are currently tagged "deprecated", others are tagged "@deprecated", and others are tagged with both.
  • Some issues that use one or both of those tags are about removing usages of deprecated code. Others are about proposing to deprecate code that isn't yet deprecated.
  • Neither tag has a description on d.o. or is documented on https://www.drupal.org/issue-tags/topic.

Proposed resolution

?

Remaining tasks

  • Decide on the desired meaning of these tags. For example, maybe "deprecated" should mean "remove deprecated usages" and "@deprecated" should mean "mark things @deprecated that aren't yet marked as such"?
  • Decide if we want to rename the tags to be more clear as to their meaning.
  • Document the meanings somewhere, such as on https://www.drupal.org/issue-tags/topic.

User interface changes

API changes

Data model changes

Problem/Motivation

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

effulgentsia created an issue.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented

I think having both deprecated and @deprecated and having them mean different things is super confusing. I'd have one tag and accept that for now we're going to have a mix of clean up work and future work. The thing is that once all deprecations are accompanied by an @trigger_error the clean up work is finally over so the tag will only mean things about future deprecation.

catch’s picture

catch
he/him
Primary language English
commented

I don't think we need tag about new deprecations. The only case where an issue is mainly about a new deprecation would be when we discover dead or nearly dead code, but if we want a tag for something like that we could use 'refactoring' or the existing clean up tags or whatever's mostly in use for that.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

As side note, Topical issue tags says to list general-purpose tags that aren't specific to any particular project issue, but that description suits also most of the tags listed in Special issue tags.

Maybe we should document the issue tags in a single page, and make clear which issue tags are specific for Drupal core, and which are generic for any issue queue associated with a module/theme.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Regarding #4, we are going to get rid of both of those pages and have one combined view of all tags with descriptions. Probably coming soon. See #2934673: Replace issue tag descriptions with a View