<div dir="auto">+Joni</div><div class="gmail_extra"><br><div class="gmail_quote">On Mar 23, 2017 12:19 PM, "Liz Henry (:lizzard)" <<a href="mailto:ehenry@mozilla.com">ehenry@mozilla.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>This issue is serious enough that fixing it should be a high priority for Firefox 52 as well as a blocking issue for the release of 53. I see this as breaking a major user-facing part of our product. <br><br></div><div>How about this as an option: walking back to Kitsune immediately, until the new system is fixed *and tested* by Firefox QE. Is that possible and what would it take to switch back to our working system? <br></div><div><br></div>Best<br><br></div>Liz<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 23, 2017 at 7:06 AM, Johann Hofmann <span dir="ltr"><<a href="mailto:jhofmann@mozilla.com" target="_blank">jhofmann@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
As mentioned in the bug, this also affects most security information
such as cert error pages and the in-content insecure password
warning.<br>
<br>
The fact that it takes a long time to get this issue fixed does not
speak in favor of the migration. I would really like to see an
official statement explaining the reasons we are dropping Kitsune.<br>
<br>
What is unclear to me:<br>
<br>
- Why was the decision to make us depend on a proprietary
third-party vendor done without feedback or announcement to any
other part of the organization?<br>
- It seems like there were at not point any Firefox engineers
involved in this. Why did nobody cross-check with the Firefox
Owner/Peers?<br>
- No Mozilla developers were involved in testing the new platform
before it went live. Testing was done by the marketing team. I can
understand that resources may be limited for maintenance, but why
was it decided that no engineers can be spared to integration test
the new platform?<br>
- Is this decision in line with the module owners of SUMO?<br>
<br>
Absurdly, the modules page lists the owners of SUMO as the
maintainers of Kitsune (<a class="m_-969050471381021253m_2575385075813207388moz-txt-link-freetext" href="https://wiki.mozilla.org/Modules/All#Sumo" target="_blank">https://wiki.mozilla.org/Modu<wbr>les/All#Sumo</a>).
Is this no longer up to date? I'd like to think the lack of
communication around this is in violation of our governance
policies.<span class="m_-969050471381021253HOEnZb"><font color="#888888"><br>
<br>
Johann</font></span><div><div class="m_-969050471381021253h5"><br>
<br>
<div class="m_-969050471381021253m_2575385075813207388moz-cite-prefix">On 23/03/2017 14:29, Sylvestre Ledru
wrote:<br>
</div>
<blockquote type="cite">
<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="m_-969050471381021253m_2575385075813207388moz-cite-prefix">Le 23/03/2017 à 14:26, Dão Gottwald a
écrit :<br>
</div>
<blockquote type="cite">
<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" target="_blank">https://bugzilla.mozilla.org/s<wbr>how_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="m_-969050471381021253m_2575385075813207388mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
firefox-dev mailing list
<a class="m_-969050471381021253m_2575385075813207388moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a class="m_-969050471381021253m_2575385075813207388moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a>
</pre>
</blockquote>
WIW<br>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="m_-969050471381021253gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div>----<br></div>Liz Henry (:lizzard)<br></div><div>Firefox Release Manager<br></div><a href="mailto:lhenry@mozilla.com" target="_blank">lhenry@mozilla.com</a><br></div></div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/firefox-dev</a><br>
<br></blockquote></div></div>