On 10/23/19 10:24 PM, Emma Humphries wrote:
Will this make it easier for non-staff contributors to get their change
sets reviewed and landed?
What else should we be doing for that.
I have some ideas I'm working on for views in Bugzilla to help with that so
that contributors can see what's going on, and where they can take action
to help.
Somewhat unrelatedly, I think the most common issue I see with new
contributors is they failing to set a reviewer. That means that their
patch goes completely unnoticed... In that case not sure what can help,
other than some of us noticing :/
I'm sure this is not a new problem though... That being said, it's a
legit use-case, IMO, to update a WIP patch to phabricator without a
reviewer, for example, to avoid spamming...
Maybe tools like moz-phab could suggest reviewers, or have a warning for
the "no reviewers" case?
-- Emilio
-- Emma
On Wed, Oct 23, 2019 at 8:56 AM glob <g...@mozilla.com> wrote:
It's available now - make sure you're running the latest version by
running `moz-phab self-update`.
-glob
Henrik Skupin wrote on 23/10/19 11:49 pm:
Piotr Zalewa wrote on 22.10.19 17:25:
Since today MozPhab does not require Arcanist to submit patches in all
supported VCS's. It's an optional and experimental feature. Add the
`--no-arc` option to switch it on.
Great to hear, but is there also an ETA when this mode will be available
for users of Mercurial? When I use this option I get:
NotImplementedError: Mercurial revisions can't be submitted without
Arcanist
Thanks
--
glob — engineering workflow — moz://a
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
