<div dir="ltr">+teampractices and wikitech-l for more input</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 16, 2013 at 11:22 AM, Arthur Richards <span dir="ltr"><<a href="mailto:arichards@wikimedia.org" target="_blank">arichards@wikimedia.org</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">I generally agree with James'/VE's approach. I'm not sure we can reasonably come up with a sound metric (eg 'degredation that affects roughly one percent of users') as it may not always be easily measurable. I think a gut-check, qualitative assessment should suffice for these kinds of issues, and can probably be broken into a few buckets:<div>
<br></div><div>*) critical functionality is BROKEN (eg edits are not being saved, article content is not accessible), there is a security concern, or a legal issue - this needs to be fixed ASAP, like possibly before the next lightning deploy</div>
<div>*) semi-critical functionality is broken but doesn't impede basic usage of critical site components (imo: reading, editing [in that order]) - (eg the watchlist star on an article doesn't accurately indicate if an article is being watched) - fixed and backported with earliest possible lightning deploy window</div>
<div>*) annoyances (styling not quite right, obscure javascript errors), non-security/legal issues in beta/alpha versions - fixed with next deployment train</div><div><br></div><div>This has generally been our approach to date on the mobile web team, although I don't think we've ever been explicit about a rubric.</div>
</div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 1:53 PM, James Forrester <span dir="ltr"><<a href="mailto:jforrester@wikimedia.org" target="_blank">jforrester@wikimedia.org</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 class="gmail_default" style="font-family:arial,helvetica,sans-serif">Kenan,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
For VE we backport (cherry pick) fixes of major issues ASAP (generally by grabbing the next available Lightning Deploy window after we've tested it), but for inconveniences (i.e., things not quite as intended but still workable, or only affecting a few users) we generally just go for the next week's deployment train instead. Otherwise, yeah, they just join the backlog.</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">J.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div>
On 15 October 2013 13:49, Kenan Wang <span dir="ltr"><<a href="mailto:kwang@wikimedia.org" target="_blank">kwang@wikimedia.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
<div dir="ltr">Hey,<div><br></div><div>The mobile team just got onto the deployment train. We're currently looking to understand what we do when we find bugs caused by the previous release during the deployment train. I proposed a three tiered triage system to my team: </div>
<div><br></div><div><div style="font-family:arial,sans-serif;font-size:13px">Current train: degradation that affects roughly one percent of users in a noticeable way</div><div style="font-family:arial,sans-serif;font-size:13px">
Current iteration, next train: degradation that affects less than one percent of users in a noticeable way</div><div style="font-family:arial,sans-serif;font-size:13px">Backlog: degradation that affects less than .1 percent of users in a noticeable way, or affects users in a cursory way</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">But was wondering if there were any other systems that teams had in place to deal with this issue.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Also, if you fix a bug does your team typically deploy during the next deployment window available or do you wait to deploy until you have a couple of fixes?</div>
<span><font color="#888888">
<div><br></div>-- <br><div dir="ltr"><div><br></div><div>Kenan Wang<br></div><div>Product Manager, Mobile</div><div>Wikimedia Foundation</div></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
Wmfproduct mailing list<br>
<a href="mailto:Wmfproduct@lists.wikimedia.org" target="_blank">Wmfproduct@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/wmfproduct" target="_blank">https://lists.wikimedia.org/mailman/listinfo/wmfproduct</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>James D. Forrester<br>Product Manager, VisualEditor<br>Wikimedia Foundation, Inc.<br><br><a href="mailto:jforrester@wikimedia.org" target="_blank">jforrester@wikimedia.org</a> | @jdforrester
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>Arthur Richards<div>Software Engineer, Mobile</div><div>[[User:Awjrichards]]</div><div>IRC: awjr</div><div>
<a href="tel:%2B1-415-839-6885%20x6687" value="+14158396885" target="_blank">+1-415-839-6885 x6687</a></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Arthur Richards<div>Software Engineer, Mobile</div><div>[[User:Awjrichards]]</div><div>IRC: awjr</div><div>+1-415-839-6885 x6687</div>
</div>