Add Q3 Goal - reduce "random" errors/bugs

[Luke Crouch]

All,

I think we've all spoken at times about our pesky "random" errors -
caching, false kumascript errors, etc.

I know we're a month into Q3, but James and I would like to add a Q3 dev
goal to reduce these "random" kinds of bugs that are typically caused by
race conditions around page moving, rendering, etc.

Does anyone object to us adding this as a Q3 goal that James will own?

Obviously we may not get to fix everything in Q3, so what are a couple
of the most annoying "random" errors and bugs that we should include in
our goal?

Thanks,
-L

[Eric Shepherd]

I think this is an important goal and I support it wholeheartedly!

Eric Shepherd
Sent from my iPhone

> _______________________________________________
> dev-mdn mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdn

[David Bruant]

Le 01/08/2013 19:04, Luke Crouch a écrit :
> All,
>
> I think we've all spoken at times about our pesky "random" errors -
> caching, false kumascript errors, etc.
>
> I know we're a month into Q3, but James and I would like to add a Q3
> dev goal to reduce these "random" kinds of bugs that are typically
> caused by race conditions around page moving, rendering, etc.
>
> Does anyone object to us adding this as a Q3 goal that James will own?

Certainly not me!
Maybe that's obvious, but beyond fixing these bugs, adding regression
tests so they don't come back should be part of the new goal IMHO.

Thanks,

David

[Eric Shepherd]

On 2013-08-02 20:30:14 +0000, David Bruant said:

> Maybe that's obvious, but beyond fixing these bugs, adding regression
> tests so they don't come back should be part of the new goal IMHO.

+1000

--
Eric Shepherd
Developer Documentation Lead
Mozilla
Blog: http://www.bitstampede.com/
Twitter: @sheppy

[Luke Crouch]

UPDATE:

After discussion, we're looking at the following main areas to refactor
to pay down technical debt that can cause lots of frustrating bugs:

* Page moving
Tacking bug 902599 [1] already has a couple bugs underneath it, and
James is already working on the first. This covers things like strange
breadcrumbs after page moves and issues with moving large sets of pages
around

* KumaScript rendering
This is huge and touches caching AND celery task code involved in every
single wiki save operation.

* Caching
This is more general caching issues - especially using memcache to give
us better consistency across web-heads and enables better code in the
future like session-backed csrf protection.

We already have bug 900961 in the board, so we're going to commit to
Page moving for sure.

Which of the others should we do? KumaScript rendering or Caching?

-L

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=902599

[Eric Shepherd]

I think the KumaScript rendering needs the attention more, and will give us more bank for our buck, sooner.

On August 8, 2013 at 11:08:00 AM, Luke Crouch (lcr...@mozilla.com) wrote:

Which of the others should we do? KumaScript rendering or Caching? 

-- 
Eric Shepherd
Developer Documentation Lead
Mozilla
Blog: http://www.bitstampede.com/

Twitter: http://www.twitter.com/sheppy

[John Karahalis]

To invoke the S of SMART, can you provide a list of specific bugs that should be completed in Q3? Would prefer not to include trackers, because a tracker can grow without limits, and at any time.

I want to be sure we know exactly what our goal is, so that we can say with certainty at the end of the quarter whether we accomplished it, rather than something wishy-washy like "We made KumaScript a bit better" or "We did a pretty good job improving page moving."

--
John Karahalis
Mozilla
openjck.com

----- Original Message -----

[Luke Crouch]

For the page move, I filed a tracker bug with 2 blocker bugs underneath. [1]

We should do the same for KumaScript - pick some KumaScript bugs to file
under a new tracker bug for the quarter. And by "we" here I mean John
and James. :)

-L

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=902599

On 8/9/13 12:55 PM, John Karahalis wrote:
> To invoke the S of SMART, can you provide a list of specific bugs that
> should be completed in Q3? Would prefer not to include trackers,
> because a tracker can grow without limits, and at any time.
>
> I want to be sure we know exactly what our goal is, so that we can say
> with certainty at the end of the quarter whether we accomplished it,
> rather than something wishy-washy like "We made KumaScript a bit
> better" or "We did a pretty good job improving page moving."
>
> --
> John Karahalis
> Mozilla
> openjck.com
>
>

> ------------------------------------------------------------------------
>
> *From: *"Eric Shepherd" <eshe...@mozilla.com>
> *To: *dev...@lists.mozilla.org, "Luke Crouch" <lcr...@mozilla.com>
> *Cc: *"Stormy Peters" <spe...@mozilla.com>
> *Sent: *Thursday, August 8, 2013 12:03:25 PM
> *Subject: *Re: Q3 Technical Debt goals (Was: Add Q3 Goal - reduce

[John Karahalis]

Fine by me, as long as we commit to the /dependencies/ and not the tracker bug. Like I said, tracker bugs can grow without limit at any time, making the M of SMART unattainable.

Please let me know what these bugs are after they are filed.

--
John Karahalis
Mozilla
openjck.com

----- Original Message -----

> > ----- Original Message -----
>

> > > From: "Eric Shepherd" <eshe...@mozilla.com>
> >
>

> > > To: dev...@lists.mozilla.org , "Luke Crouch" <lcr...@mozilla.com>
> >
>
> > > Cc: "Stormy Peters" <spe...@mozilla.com>
> >
>
> > > Sent: Thursday, August 8, 2013 12:03:25 PM
> >
>
> > > Subject: Re: Q3 Technical Debt goals (Was: Add Q3 Goal - reduce "random"