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.
Description
Description
Related Objects
Related Objects
- Mentioned Here
- T227665: Announce or revert ResultWrapper iteration change
Event Timeline
Comment Actions
(Thought of this while thinking about what projects to add to T227665: Announce or revert ResultWrapper iteration change.)
Comment Actions
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...
Comment Actions
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.
Comment Actions
I guess my question is who is committed to triaging all incoming tasks and to constantly remember and set this keyword tag appropriately, while also having the knowledge to understand that some change breaks backwards compatibility. If search results for tasks with that keyword are too incomplete, then "would make it vastly easier to search for the cause when one updates a wiki or an extension" won't work.
Comment Actions
I'm going to boldly decline this per last comment. Please reopen if there are new arguments or aspects that have not been brought up yet.