Skip to content

Emphasize new features go in higher tiers, but lower when necessary and without hesitation

Shaun McCann requested to merge shaunmccann-master-patch-76353 into master

Why is this change being made?

This is the second part of an MR to emphasize that new features should go into higher tiers but we should not hesitate to reduce, and/or open source, features once we identify they should be in a lower tier. This MR adds a brief description and a link to the "Determining the tier of a new feature" in the Product handbook.

This is linked to a previous MR emphasizing that we should not hesitate to open source features:

!43099 (diffs)

Does this MR meet the acceptance criteria?

Assign to DRI

  • Did you assign this change to the correct DRI of the page or information you are changing?

Conformity

Merge request reports