Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

5/22 sprint planning - send me bugs!

1 view
Skip to first unread message

Les Orchard

unread,
May 8, 2012, 2:44:23 PM5/8/12
to dev...@lists.mozilla.org, Ali Spivak
CC'ing the dev-mdn list, which should be more inclusive.

-------- Original Message --------
Subject: 5/22 sprint planning - send me bugs!
Date: Tue, 8 May 2012 11:25:47 -0700 (PDT)
From: Ali Spivak <asp...@mozilla.com>

If you have any bugs you think should/could go into the sprint planning
session tomorrow, pls send on to me and I'll add them to the list for
discussion!

Les Orchard

unread,
May 8, 2012, 3:12:05 PM5/8/12
to dev...@lists.mozilla.org, Ali Spivak
On 5/8/12 2:44 PM, Les Orchard wrote:
> If you have any bugs you think should/could go into the sprint planning
> session tomorrow, pls send on to me and I'll add them to the list for
> discussion!

Some candidates from me:

* kumascript: Improve caching for kuma -> kumascript
https://bugzilla.mozilla.org/show_bug.cgi?id=747154

* kumascript: Improve caching for kumascript -> kuma requests
(was in the previous sprint, but webdev offsite distracted me)
https://bugzilla.mozilla.org/show_bug.cgi?id=747151

* kumascript: Optimize wiki.page
(this one already has a PR awaiting review)
https://bugzilla.mozilla.org/show_bug.cgi?id=747166

Once those are squashed, the last one blocking completion of KumaScript
overall is wrapping up deployment in bug 730505:
https://bugzilla.mozilla.org/show_bug.cgi?id=730705

FWIW, we're getting really close to killing off all the known blockers
to a serious evaluation of Kuma launch readiness:


https://bugzilla.mozilla.org/showdependencytree.cgi?id=710713&hide_resolved=1

Once that list is exhausted of open bugs and we have a working
full-stack staging server, we can be more confident letting people bang
on Kuma and shake out the lurking unknown bugs.

--
lorc...@mozilla.com
http://lmorchard.com
{web,mad,computer} scientist


0 new messages