<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello</p>
<p>FWIW, this has been a very important source of issue and
frustration for the release management team too.</p>
<p>This added some frictions at the end of the 52 release cycle.<br>
</p>
<p>Sylvestre<br>
</p>
<br>
<div class="moz-cite-prefix">Le 23/03/2017 à 14:26, Dão Gottwald a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CACV3tyucUd-925zj-k2D1qLPqSMxWd=s_jE=w_8Hk=6zOnZ1zQ@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>Apparently in-product links to SUMO have been broken in
non-en-US builds for at least two weeks:<br>
<br>
<a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6"
moz-do-not-send="true">https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6</a><br>
<br>
</div>
Two weeks passing without a resolution to this seems
unacceptable.<br>
<br>
</div>
Why have we switched SUMO to third-party software and pulled
our own engineers without at least announcing this decision
through the appropriate channels (this includes this mailing
list) to allow people to voice concerns as to what this means
for our products?<br>
<br>
</div>
<div>Can we switch back from Lithium and resource SUMO
appropriately again?<br>
</div>
<div><br>
</div>
dao<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
WIW<br>
</body>
</html>