Confirmed users
1,989
edits
Phabricator/Bugzilla Equivalents: Difference between revisions
Jump to navigation
Jump to search
m
Phabricator/Bugzilla Equivalents (view source)
Revision as of 14:35, 6 February 2019
, 6 February 2019→Watch a component
(Finish off last WIP items.) |
|||
| Line 87: | Line 87: | ||
== Watch a component == | == Watch a component == | ||
Phabricator has a notification system, [https://phabricator.services.mozilla.com/herald/ Herald], which allows you to create custom notification rules. This can be used to subscribe yourself to revisions that touch certain parts of the code base, or even add yourself as a reviewer. You can view example rules other user's have created [https://phabricator.services.mozilla.com/herald/query/all/ here]. | Phabricator has a notification system, [https://phabricator.services.mozilla.com/herald/ Herald], which allows you to create custom notification rules. This can be used to subscribe yourself to revisions that touch certain parts of the code base, or even add yourself as a reviewer. You can view example rules other user's have created [https://phabricator.services.mozilla.com/herald/query/all/ here]. | ||
== How do I deal with non-mozilla branch patches after bugzilla review flags are disable on components on Feb 28? == | |||
In the announcement, it states | |||
Initially, only code landing in mozilla-central will be required to be reviewed in Phabricator. Once we have implemented more processes in Phabricator, we will move reviews of all of the mozilla-central “branches” to Phabricator. | |||
What does this mean for cases where a separate branch patch needs to be written after Feb 28 before it's possible to review the other branches in Phabricator? | |||
You can review anything Phabricator, however Lando can't land to the other "branches" at this time. Uplift approval will also be moved at a later date. | |||