kuma launch status

[Ali Spivak]

Hi all,

Wanted to give the current status of the kuma launch. We're continuing to experience issues on the kuma servers and have several major bugs open. Specifically, we are having trouble with platform stability which has kept us on only one web server (out of 3); we have not closed out the launch checklist ( bug 771763 ) or security review ( bug 662860 ); and we still need to do some migration work ( bug 773381 ). Based on this, we've decided to delay the launch until we can resolve (it sounds like a big list, but we're plugging away and expect most of the issues to be closed by EOD Monday).

I am, however, not projecting a new date at this point, as the whole team feels that we need to get a handle on bugs and stability and then determine when it makes sense to go live (I agree). I want to apologize for the uncertainty and delays - the dev and IT teams are doing really amazing work to try to resolve the problems, but issues just keep popping up. We are making progress, but also want to make sure the new platform is indeed an improvement when it goes live.

So, what now?

The dev team will be meeting each morning to check in, review the issues, and set goals for the day, as well as evaluate any new bugs that might have come in the day before.

Every other day, we will do a launch readiness assessment, where we will look at the status of the open bugs as well as platform stability and make a ready or not decision. If not ready, we'll continue on and meet 2 days later to re-assess; then rinse and repeat until we say "go." Once we make the go decision, we'll let everyone know the launch date - which will include a few quiet days after all the code has been pushed to be absolutely confident that this thing is stable and ready for action. Then, we'll push it live and Deki will be history. This all, of course, assumes nothing catastrophic happens to Deki during this process - we're hoping that doesn't happen, but we have a plan in place for that if it does. Thanks for sticking with us during this process - we're already hearing good things about kuma from the community who has been testing it, and are looking forward to bringing improvements to the MDN wiki when we (finally) launch.

please let me know if you have any questions,
ali




ali spivak
MDN Product Manager, Mozilla
408-859-8260
asp...@mozilla.com

[Jeremie Patonnier]

Hi!

Just a word to say that the whole team is doing an amazing job. Keep going,
Kuma already rocks, thank you all :)

_o/\o/\o_

++
Jérémie

2012/7/13 Ali Spivak <asp...@mozilla.com>

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



--
Jeremie
.............................
Web : http://jeremie.patonnier.net
Twitter : @JeremiePat <http://twitter.com/JeremiePat>

[Axel Hecht]

Thanks for the update.

Are you going to keep mdn in read-only mode during that time?

Axel

[Ali Spivak]

Yes - we'll be moving editing to the new platform as soon as we can, but in the meantime we need to keep editing off so the two instances don't get out of synch. We're really hoping this isn't for too long - if it starts stretching out we'll take a look into alternatives.

ali

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

[Ali Spivak]

oh, just to make sure everyone knows, you can edit on developer-new (https://developer-new.mozilla.org/en-US/) & the edits will be kept when the site goes live (developer-new is the new production, we just haven't switched the domains yet because it's still a bit buggy).



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

[Sheppy]

Yes, it's worth noting that you can edit on https://developer-new.mozilla.org/ -- this is in fact the new production server, it's just not yet quite stable/finished enough to make the default. We hope to be there very soon.

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