<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Additionally, it seems I now get emails for review requests from
Differential but I still don't get CC'd on the bug automatically
when this happens. This is annoying because (a) the email contents
need improvement (I filed
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1467726">https://bugzilla.mozilla.org/show_bug.cgi?id=1467726</a> ) and (b)
because the email lacks context, I do too.<br>
</p>
<p>Differential creates an attachment on the bug when a revision is
created, can it also CC the reviewers on the bug when this
happens, or was there an explicit decision not to do so? Then at
least I can immediately open the bug from the link in the email
bmo sends me for that, given the differential email doesn't
include such a link...</p>
<p>More generally, the email coming from somewhere else breaks
threading (ie review requests are now not in 1 thread with the
rest of the bugmail for a bug in my email client), but I assume
there's no way we can fix that unless we start using bmo r? flags
(which AIUI is an explicit non-goal?)... :-(</p>
<p>~ Gijs<br>
</p>
<div class="moz-cite-prefix">On 06/06/2018 15:57, Mark Côté wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPJZ0qRG5Qe0dHV6WNZ4PPpoOTzMD7jEzb6DMWfgw=eXwR-21g@mail.gmail.com">
<div dir="ltr">The Engineering Workflow team is happy to announce
the release of Phabricator and Lando for general use. Going
forward, Phabricator will be the primary code-review tool for
modifications to the mozilla-central repository, replacing both
MozReview and Splinter. Lando is an all-new automatic-landing
system that works with Phabricator. This represents about a year
of work integrating Phabricator with our systems and building
out Lando. Phabricator has been in use by a few teams since last
year, and Lando has been used by the Engineering Workflow team
for several weeks and lately has successfully landed a few
changesets to mozilla-central.<br>
<br>
Phabricator is a suite of applications, but we are primarily
using the code-review tool, called Differential, which will be
taking the place of MozReview and Splinter. Bug tracking will
continue to be done with Bugzilla, which is integrated with
Phabricator. You will log into Phabricator via Bugzilla. We will
soon begin sunsetting MozReview, and Splinter will be made
read-only (or replaced with another patch viewer). An upcoming
post will outline the plans for the deprecation, archival, and
decommission of MozReview, with Splinter to follow.<br>
<br>
I also want to thank Phacility, the company behind Phabricator,
who provided both excellent support and work on Phabricator
itself to meet our requirements in an exceptionally helpful and
responsive way.<br>
<br>
User documentation on Phabricator catered specifically to
Mozillians can be found at <a
href="https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html"
moz-do-not-send="true">https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html</a>.
It is also linked from within Phabricator, in the left-hand menu
on the home page.<br>
<br>
User documentation on Lando can be found at <a
href="https://moz-conduit.readthedocs.io/en/latest/lando-user.html"
moz-do-not-send="true">https://moz-conduit.readthedocs.io/en/latest/lando-user.html</a>.<br>
<br>
MDN documentation is currently being updated.<br>
<br>
At the moment, Phabricator can support confidential revisions
when they are associated with a confidential bug, that is, a bug
with one or more security groups applied. Lando, however, cannot
currently land these revisions. This is a limitation we plan to
fix in Q3. You can follow <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1443704"
moz-do-not-send="true">https://bugzilla.mozilla.org/show_bug.cgi?id=1443704</a>
for developments. See <a
href="http://moz-conduit.readthedocs.io/en/latest/phabricator-user.html#landing-patches"
moz-do-not-send="true">http://moz-conduit.readthedocs.io/en/latest/phabricator-user.html#landing-patches</a>
for our recommendations on landing patches in Phabricator
without Lando.<br>
<br>
Similarly, there are two other features which are not part of
initial launch but will follow in subsequent releases:<br>
* Stacked revisions. If you have a stack of revisions, that is,
two or more revisions with parent-child relationships, Lando
cannot land them all at once. You will need to individually
land them. This is filed as <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1457525"
moz-do-not-send="true">https://bugzilla.mozilla.org/show_bug.cgi?id=1457525</a>.
<br>
* Try support. Users will have to push to the Try server
manually until this is implemented. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1466275"
moz-do-not-send="true">https://bugzilla.mozilla.org/show_bug.cgi?id=1466275</a>.
<br>
<br>
Finally, we realize there are a few oddities with the UI that we
will also be fixing in parallel with the new features. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1466120"
moz-do-not-send="true">https://bugzilla.mozilla.org/show_bug.cgi?id=1466120</a>.<br>
<br>
The documentation lists several ways of getting in touch with
the Engineering Workflow team, but #phabricator and #lando on
IRC are good starting points.<br>
<br>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
firefox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
</blockquote>
</body>
</html>