Skip to content

Update and document relationships between extensions #92

@zimeon

Description

@zimeon

Editors propose removing "Obsoletes" and "Obsoleted by" from the headers of extensions, and instead replacing for any cases where there is a relation with a new line:

For 0001:

For 0003 (soon, when #86 approved):

and allowing the possibility of multiple relationships:

  • Related to nnnn-ext-a (obsoletes), mmmm-ext-b (extended by)

This approach requires an update to the headers section of the repository README. To document the approach and list the set of relationships supported along with their intended use. For now we propose:

  • obsoletes - Use when a new extension SHOULD be used in preference to the prior extension. This may be because it corrects errors, or updates a canonical list, for example.
  • obsoleted by - Inverse of obsoletes, both MUST be used together.
  • extends - Use when a new extension adds but does not remove functionality compared to a prior extension, and there is nothing to suggest that use of the prior extension SHOULD be avoided.
  • extended by - Inverse of extends, both MUST be used together.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions