<div dir="ltr">Hi guys,<div><br></div><div>Quick update here: Roxana has been working on the script today, and it seems she got pretty much everything set up, and only needs to fix some certificate issue to have it working. We expect to have the test results for you tomorrow, as Roxana had to leave.</div><div><br></div><div>Regards,</div><div>Florin.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 10:33 AM, Florin Mezei <span dir="ltr"><<a href="mailto:fmezei@mozilla.com" target="_blank">fmezei@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 dir="ltr">Thank you Roland! I've forwarded all the information to Roxana from the Platform QA team, who will have a look at this today.<div><br></div><div>Regards,</div><div>Florin.</div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 10:25 AM, Roland moco Tanglao <span dir="ltr"><<a href="mailto:rtanglao@mozilla.com" target="_blank">rtanglao@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 bgcolor="#FFFFFF" text="#000000">
<p>HI Florin and QA team</p>
<p>The URL being redirect to is on PRODUCUCTION NOT on stage so I've
revised my testing HOW TO appropriately. Please refer to [1] when
testing.</p>
<p>Cheers!</p>
<p>...Roland</p>
<p>[1]
<a class="m_8050020391402001694m_2364567945965159555moz-txt-link-freetext" href="https://github.com/rtanglao/rt-li-sumo-redirects/blob/master/how-to-test-6000-redirects.md" target="_blank">https://github.com/rtanglao/rt<wbr>-li-sumo-redirects/blob/master<wbr>/how-to-test-6000-redirects.md</a></p>
<p>
</p>
<p>From <a href="https://supportcases.lithium.com/5006100000AawTs" target="_blank">Case
00137762</a></p>
<p>Note this is automatable (I am 99% sure) via a script. Here is a
<a href="https://github.com/rtanglao/rt-li-sumo-redirects/blob/master/get-stage-url.rb" target="_blank">proof
of concept in Ruby</a>.</p>
<ul>
<li>1. For each of the approximately 6100 rows in the spreadsheet
at: <br>
<a href="https://docs.google.com/spreadsheets/d/1bqoCUqsCvdrGTXssavzdadTRF38l8JoIjuEJxqc2QiU/edit#gid=277128454" target="_blank">https://docs.google.com/spread<wbr>sheets/d/1bqoCUqsCvdrGTXssavzd<wbr>adTRF38l8JoIjuEJxqc2QiU/edit#<wbr>gid=277128454</a>
<ul>
<li>A. Please test the redirection of the links in Column D to
the Target URL in Column G as follows:
<ul>
<li>i) In the URL from Column D "Redirect this Link" e.g.
row 2 <code><a class="m_8050020391402001694m_2364567945965159555moz-txt-link-freetext" href="https://support.mozilla.org/kb/insecure-password-warning-firefox-ach" target="_blank">https://support.mozilla.org/kb<wbr>/insecure-password-warning-fir<wbr>efox-ach</a></code><br>
replace <code>support.mozilla</code> with <code>support-stage.allizom</code>
e.g. row 2, Column D -> <br>
<code><a class="m_8050020391402001694m_2364567945965159555moz-txt-link-freetext" href="https://support-stage.allizom.org/kb/insecure-password-warning-firefox-ach" target="_blank">https://support-stage.allizom.<wbr>org/kb/insecure-password-warni<wbr>ng-firefox-ach</a></code>
<br>
Let's call this <code>URL 1</code></li>
<li>ii) Take the URL from Column G "Target URL" e.g. row 2
<code><a class="m_8050020391402001694m_2364567945965159555moz-txt-link-freetext" href="https://support.mozilla.org/t5/Protect-your-privacy/Insecure-password-warning-in-Firefox/ta-p/27861" target="_blank">https://support.mozilla.org/t5<wbr>/Protect-your-privacy/Insecure<wbr>-password-warning-in-Firefox/<wbr>ta-p/27861</a></code>
Let's call this <code>URL 2</code></li>
<li>iii) Load <code>URL 1</code> in Firefox</li>
<li>iv) If Firefox redirects to <code>URL 2</code>, THEN
test PASS ELSE test FAIL</li>
</ul>
</li>
</ul>
</li>
</ul><div><div class="m_8050020391402001694h5">
<br>
<div class="m_8050020391402001694m_2364567945965159555moz-cite-prefix">On 3/28/17 9:53 PM, Mahendranadh
Potharaju wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div><b>Status Update : </b><br>
<br>
</div>
<div>The interim fix is in place on staging server and
available for QA to test. After QA validation we
will roll out changes to production OR based on
severity of any issues, switch to Kitsune. <br>
</div>
<div><br>
</div>
<div>For the permanent solution : <br>
</div>
Firefox dev team and Lithium dev team had met
yesterday and now have a good understanding of the
issues in this implementation. Lithium dev team is
going to present a solution by Tuesday(4/4/17) or
Wednesday (4/5/17) and we will then plan its
implementation. <br>
</div>
<br>
</div>
Currently we are on course with intermix fix to have the
links fixed in this week. <br>
<br>
</div>
Thanks everyone for giving this the right attention and
bringing it back on track. <br>
<br>
</div>
Regards, <br>
<br>
</div>
Mahe<br>
<div>
<div>
<div>
<div> <br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 24, 2017 at 11:27 AM,
Mahendranadh Potharaju <span dir="ltr"><<a href="mailto:mpotharaju@mozilla.com" target="_blank">mpotharaju@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 dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Here is status update from our call
this morning<br>
<br>
</div>
<div><b>Current Action Items : </b><br>
</div>
<ul>
<li>Joni is working on the links and
will hand over to Lithium for the
migration by eod Friday 3/24.</li>
<li>Lithium should be able to complete
migration on Tuesday 3/28</li>
<li>QA team has been reached to plan
testing the SUMO links on Wednesday
3/29</li>
</ul>
<p><b>Backup Plan </b><br>
</p>
</div>
</div>
</div>
<ul>
<li>Patrick McClard is gauging the work to
migrate new content (questions, articles
etc) in Lithium since the switch over. </li>
<li>Monday, 3/27 -Giorgos will provide a
time estimate to stand up Kitsune again
and the DNS change </li>
<li>If Lithium isn't able to migrate links
in time or QA team fails the migration, we
will switch over to Kitsune and figure out
next course of action with Lithium. <br>
</li>
</ul>
</div>
<b><br>
</b></div>
There seems to be few more links from <a href="http://mozilla.org" target="_blank">mozilla.org</a> and other sites
which could be broken. Am reaching David Tenser to
see who can help here to identify and how we can
fix. <br>
<br>
</div>
Alex and Jascha are in contact with Lithium folks
and are helping getting the necessary attention and
resources. <br>
<br>
</div>
We will do daily check-ins and intend to have the
links all up next week. Feel free to reach back with
any questions. <br>
<br>
</div>
Thanks, <br>
<br>
</div>
Mahe<br>
</div>
<div class="gmail_extra">
<div>
<div class="m_8050020391402001694m_2364567945965159555h5"><br>
<div class="gmail_quote">On Thu, Mar 23, 2017 at 1:51
PM, Giorgos Logiotatidis <span dir="ltr"><<a href="mailto:giorgos@mozilla.com" target="_blank">giorgos@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+
Benjamin Sternthal<br>
<span><br>
<br>
Madalina Ana writes:<br>
<br>
> + Patrick and rest of the SUMO staff<br>
><br>
> Just to clarify, we're due to finalize the
spreadsheets tomorrow and send<br>
> for implementation, implementation might
take a few days longer.<br>
><br>
> Let's check-in tomorrow 8:45 Am Pacific,
I'll send out an invite.<br>
><br>
> We're working on getting proper contacts
for Lithium dev so that we can<br>
> connect you.<br>
><br>
> I'll be offline for the rest of today as
I'm in CET, if you need any<br>
> follow-up today please reach out to
Patrick.<br>
><br>
> Thanks,<br>
><br>
> Madalina<br>
><br>
> On Thu, Mar 23, 2017 at 9:06 PM,
Mahendranadh Potharaju <<br>
> <a href="mailto:mpotharaju@mozilla.com" target="_blank">mpotharaju@mozilla.com</a>>
wrote:<br>
><br>
>> Thanks for jumping on a quick call
Johann, Giorgos and Benjamin.<br>
>><br>
>> Per Madalina's update on the bug<br>
</span>>> <<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1324426</a>>Lithiu<wbr>m
is working<br>
<div>
<div class="m_8050020391402001694m_2364567945965159555m_-5307440070962056920h5">>>
on an interim fix which is due tomorrow. And,
we need to test this interim<br>
>> fix to ensure its done right.<br>
>><br>
>><br>
>> The further steps is for us to meet
with Lithium engineering team to<br>
>> identify the right permanent fix and
find owners to implement it on Firefox<br>
>> and/or Lithium. If its harder with
Lithium folks jumping on a call with us,<br>
>> seems like they are based out of SF
and we can have an in person meeting at<br>
>> Mozilla or Lithium office.<br>
>><br>
>> We'll meet tomorrow and there after
to drive this to finish.<br>
>><br>
>> Madalina - Please propose a check-in
meet time for the status.<br>
>><br>
>><br>
>> Thanks,<br>
>><br>
>> Mahe<br>
>><br>
>><br>
>> On Thu, Mar 23, 2017 at 11:55 AM,
Erin Lancaster <<a href="mailto:elancaster@mozilla.com" target="_blank">elancaster@mozilla.com</a>><br>
>> wrote:<br>
>><br>
>>> If it's not too late for you, we
are in my vidyo room we are on with some<br>
>>> other folks. Thank you so much.<br>
>>><br>
>>> On Thu, Mar 23, 2017 at 11:54 AM,
Johann Hofmann <<a href="mailto:jhofmann@mozilla.com" target="_blank">jhofmann@mozilla.com</a>><br>
>>> wrote:<br>
>>><br>
>>>> Sure, I can volunteer as a
point of contact and would forward any bigger<br>
>>>> questions to the Firefox
team.<br>
>>>><br>
>>>> Thank you for acting so
quickly on this! :)<br>
>>>><br>
>>>> Johann<br>
>>>><br>
>>>><br>
>>>> On 23/03/2017 19:34, Erin
Lancaster wrote:<br>
>>>><br>
>>>> Johann, Dão: Mahe is making
progress figuring out who is involved here<br>
>>>> and what some next steps
should be but we need a single point of
contact on<br>
>>>> the Firefox engineering team.
We don’t have any specific requests as of yet<br>
>>>> but can Mahe loop one of you
in? If not, do you have someone else you can<br>
>>>> suggest?<br>
>>>><br>
>>>> Thank you,<br>
>>>> Erin<br>
>>>><br>
>>>> On Mar 23, 2017, at 11:27 AM,
Erin Lancaster <<a href="mailto:elancaster@mozilla.com" target="_blank">elancaster@mozilla.com</a>><br>
>>>> wrote:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Thu, Mar 23, 2017 at 10:14
AM, Peter Dolanjski <<br>
>>>> <a href="mailto:pdolanjski@mozilla.com" target="_blank">pdolanjski@mozilla.com</a>>
wrote:<br>
>>>><br>
>>>>> +Joni<br>
>>>>><br>
>>>>> On Mar 23, 2017 12:19 PM,
"Liz Henry (:lizzard)" <<a href="mailto:ehenry@mozilla.com" target="_blank">ehenry@mozilla.com</a>><br>
>>>>> wrote:<br>
>>>>><br>
>>>>>> This issue is serious
enough that fixing it should be a high
priority<br>
>>>>>> for Firefox 52 as
well as a blocking issue for the release of
53. I see<br>
>>>>>> this as breaking a
major user-facing part of our product.<br>
>>>>>><br>
>>>>>> How about this as an
option: walking back to Kitsune immediately,<br>
>>>>>> until the new system
is fixed *and tested* by Firefox QE. Is that<br>
>>>>>> possible and what
would it take to switch back to our working
system?<br>
>>>>>><br>
>>>>>> Best<br>
>>>>>><br>
>>>>>> Liz<br>
>>>>>><br>
>>>>>> On Thu, Mar 23, 2017
at 7:06 AM, Johann Hofmann <<a href="mailto:jhofmann@mozilla.com" target="_blank">jhofmann@mozilla.com</a>><br>
>>>>>> wrote:<br>
>>>>>><br>
>>>>>>> As mentioned in
the bug, this also affects most security
information<br>
>>>>>>> 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<br>
>>>>>>> speak in favor of
the migration. I would really like to see an
official<br>
>>>>>>> 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<br>
>>>>>>> vendor done
without feedback or announcement to any other
part of the<br>
>>>>>>> organization?<br>
>>>>>>> - It seems like
there were at not point any Firefox engineers<br>
>>>>>>> involved in this.
Why did nobody cross-check with the Firefox
Owner/Peers?<br>
>>>>>>> - No Mozilla
developers were involved in testing the new
platform<br>
>>>>>>> before it went
live. Testing was done by the marketing team.
I can<br>
>>>>>>> understand that
resources may be limited for maintenance, but
why was it<br>
>>>>>>> decided that no
engineers can be spared to integration test
the new<br>
>>>>>>> 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<br>
>>>>>>> maintainers of
Kitsune (<a href="https://wiki.mozilla.org/Modules/All#Sumo" rel="noreferrer" target="_blank">https://wiki.mozilla.org/Modu<wbr>les/All#Sumo</a>).<br>
>>>>>>> Is this no longer
up to date? I'd like to think the lack of
communication<br>
>>>>>>> around this is in
violation of our governance policies.<br>
>>>>>>><br>
>>>>>>> Johann<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On 23/03/2017
14:29, Sylvestre Ledru wrote:<br>
>>>>>>><br>
>>>>>>> Hello<br>
>>>>>>><br>
>>>>>>> FWIW, this has
been a very important source of issue and
frustration<br>
>>>>>>> for the release
management team too.<br>
>>>>>>><br>
>>>>>>> This added some
frictions at the end of the 52 release cycle.<br>
>>>>>>><br>
>>>>>>> Sylvestre<br>
>>>>>>><br>
>>>>>>> Le 23/03/2017 à
14:26, Dão Gottwald a écrit :<br>
>>>>>>><br>
>>>>>>> Apparently
in-product links to SUMO have been broken in
non-en-US<br>
>>>>>>> builds for at
least two weeks:<br>
>>>>>>><br>
>>>>>>> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c6" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/s<wbr>how_bug.cgi?id=1324426#c6</a><br>
>>>>>>><br>
>>>>>>> Two weeks passing
without a resolution to this seems
unacceptable.<br>
>>>>>>><br>
>>>>>>> Why have we
switched SUMO to third-party software and
pulled our own<br>
>>>>>>> engineers without
at least announcing this decision through the
appropriate<br>
>>>>>>> channels (this
includes this mailing list) to allow people to
voice<br>
>>>>>>> concerns as to
what this means for our products?<br>
>>>>>>><br>
>>>>>>> Can we switch
back from Lithium and resource SUMO
appropriately again?<br>
>>>>>>><br>
>>>>>>> dao<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>>
______________________________<wbr>_________________<br>
</div>
</div>
>>>>>>> firefox-dev mailing
<a class="m_8050020391402001694m_2364567945965159555moz-txt-link-abbreviated" href="mailto:listfirefox-dev@mozilla.orghtt" target="_blank">listfirefox-dev@mozilla.orghtt</a><wbr>ps://<a href="http://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">mail.mozilla.org/listinfo<wbr>/firefox-dev</a><br>
<div class="m_8050020391402001694m_2364567945965159555m_-5307440070962056920HOEnZb">
<div class="m_8050020391402001694m_2364567945965159555m_-5307440070962056920h5">>>>>>>><br>
>>>>>>> WIW<br>
>>>>>>><br>
>>>>>>>
______________________________<wbr>_________________
firefox-dev mailing<br>
>>>>>>> list <a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>>>> nfo/firefox-dev<br>
>>>>>><br>
>>>>>> --<br>
>>>>>> ----<br>
>>>>>> Liz Henry (:lizzard)<br>
>>>>>> Firefox Release
Manager<br>
>>>>>> <a href="mailto:lhenry@mozilla.com" target="_blank">lhenry@mozilla.com</a><br>
>>>>>>
______________________________<wbr>_________________
firefox-dev mailing<br>
>>>>>> list <a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>>> nfo/firefox-dev<br>
>>>>><br>
>>>>>
______________________________<wbr>_________________
firefox-dev mailing<br>
>>>>> list <a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a href="https://mail.mozilla.org/listi" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi</a><br>
>>>>> nfo/firefox-dev<br>
>>>><br>
>>>><br>
>>><br>
>><br>
>><br>
</div>
</div>
<span class="m_8050020391402001694m_2364567945965159555m_-5307440070962056920HOEnZb"><font color="#888888">>> --<br>
>> Mahendra Potharaju<br>
>><br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
<span class="m_8050020391402001694m_2364567945965159555HOEnZb"><font color="#888888">-- <br>
<div class="m_8050020391402001694m_2364567945965159555m_-5307440070962056920gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Mahendra Potharaju<br>
</div>
</div>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="m_8050020391402001694m_2364567945965159555gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Mahendra Potharaju<br>
</div>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>