I like that idea. I'm cc'ing Raymond since he's probably not on the
list. He'll organize the WebQA stuff.
Raymond, what do you think - informal test periods after releases AND a
couple of big test days?
On 4/26/12 11:46 AM, Ali Spivak wrote:
> I'm leaning towards option 3 - have smaller, more "informal" test periods after each release that focus on testing a sub-set of code/features that were in a specific release (or bundle 2 releases together, so we test at 2 week intervals as opposed to every week), and then doing a few big test days to really bang on the specific user/feature sets. Thoughts on this approach?
> ----- Original Message -----
> From: "Luke Crouch"<lcr...@mozilla.com>
> To: "Jeremie Patonnier"<jeremie....@gmail.com>, "Alicia Spivak"<asp...@mozilla.com>, "Les Orchard"<lorc...@mozilla.com>
> Cc: "David Bruant"<brua...@gmail.com>, "Eric Shepherd"<eshe...@mozilla.com>, "engagement-developers"<email@example.com>
> Sent: Thursday, April 26, 2012 7:28:54 AM
> Subject: Re: MDN/Kuma development update
> We're developing Kuma in shadow release, so it's already live on both
> MDN staging (https://developer-stage9.mozilla.org/) and production
> (though only for specific users, if you want to test in production, let
> me know and I'll add you to the list).
> To test Kuma on staging, go to https://developer-stage9.mozilla.org/docs > - the "New Wiki Feature Preview" section. The list of all pages shows
> the "top 50" pages that we continuously migrate from MindTouch to Kuma.
> WARNING: The wiki pages on stage9 are from old data and there's also
> plenty of junk data in there. Whatever edits you make to Kuma pages will
> be blown away by the next migration run. And there are bugs. It's a
> staging server, after all. :)
> We'll soon have a (working) dev server at https://kuma-stage.mozilla.org/ >
> We're using a release train model like Firefox; we release weekly on
> Tuesday. So, code flows like so:
> Nightly/Development: kuma-stage.mozilla.org (5 minutes after landing in
> Beta/Staging: developer-stage9.mozilla.org (Tuesday)
> Release/Production: developer.mozilla.org (next Tuesday after Staging)
> Here's a few ways we could do test days:
> 1. Weekly test day every Friday(?) for the features released to staging
> on Tuesday
> 2. Periodic test days (bi-weekly?) for specific user/feature-sets
> (translation, KumaScript templates, etc.)
> 3. All of the above
> 4. Something else
> Having said all that, I'll now gladly leave it to Ali to set up the test
> days however is best for everyone.
> /me goes back to fixing kuma-stage.mozilla.org >