Page MenuHomePhabricator

Backwards compatibility break tag
Open, Needs TriagePublic

Description

I wonder if it would be useful to have a project tag for tasks that involve breaking backwards compatibility? Kind of like User-notice, but for a more specific auidence. On one hand, using it consistently would be a significant amount of mental overhead (there are only so many labels one can keep in their head to consider for each new task whether it should be tagged); on the other hand it would make it vastly easier to search for the cause when one updates a wiki or an extension and it does not work as expected, which I think is a fairly prominent use case of Phabricator for a large part of the technical community.

Event Timeline

Tgr created this task.Jul 10 2019, 1:39 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 10 2019, 1:39 PM
Tgr added a comment.Jul 10 2019, 1:41 PM

(Thought of this while thinking about what projects to add to T227665: Announce or revert ResultWrapper iteration change.)

Aklapper renamed this task from B/C break tag to Backwards compatibility break tag.Jul 10 2019, 1:52 PM
Aklapper added a comment.EditedJul 10 2019, 1:55 PM

it would make it vastly easier to search for the cause

This would only be true if enough people who break BC realize that they break BC && know about this tag && take the time to set this tag.
I already have the feeling (citation needed) that the Regression does not get set by many people. The more tags, the more you won't remember all of them...

Tgr added a comment.Jul 10 2019, 2:36 PM

Regression IMO doesn't really have a use case. Why would I want to search for known regressions?
Since it doesn't have a use case, few people care about placing it.