Websites/WebifyMe/Meeting Apr 27

From MozillaWiki
Jump to: navigation, search

Wed April 27th 1pm PST

Follow Up

Picking up from our Apr 20th meeting

  • Grace or William: Get exact peak numbers for TwitterParty to estimate peak load
    • For Web O' Wonder: They had 400,000 on the first day and slowly decreased from there. Initially averaging about 80,000-90,000 per day in the first/second week and then now averaging about 15,000 per day.
  • William: Update Goals and Metrics bug 642348
  • Stas: Will try a dry run at extracting strings, may file a bug to use Tower in the project
    • Whitespace okay, w/o tower is okay

Status Update

On where off to the races... 31 Open bugs

We're working on string freeze blockers.

Critical Path Timeline

Apr 15th - TBG Staging bugs Fixed

Apr 21th string freeze - TBD Slipped, new strings discovered in DB

Apr 25th - Webifyme-dev.allizom.org staged

Apr 26th - WebQA starts

May 9th - WebQA finishes

May 10th - Go / No Go Decision

May 11th - Prod launch

In Parallel Timeline

Apr 28th - May 6th - *at risk* L10n two weekends, three preferred (Apr 30th and May 7th)

Apr 26nd - May 6th - Operations builds out prod environment (1 week approx)

Apr 28 - May 6th - Infrasec testing (4 days approx)

Triage as needed - TBG, Grace, Krupa, ozten

Apr 15th - May 6th - TBG fixing bugs which have been reported

New Topics

Any schedule estimate updates? (IT, QA, TBG?)

TBG needs to work on Markup, so Webifyme development is going to stop for now. Claudia will give estimate of dev time. brez is sole developer covering for Markup too.

Couple new L10n bugs Claudia will get an estimate to fix these.

Grace/William to evaluate copy changes and breaking string freeze. William to update copy bugs as L10n blockers.

Who will be Admin on stage and prod? It's not clear why it exists. Claudia to write up requirements.

QA is blocked on 500 collage errors. Our contractors cannot start testing. Please move release to May 12.

Stas - L10n 2 weeks is not enough, too many strings. 3 weekends is preferred. Markup is competing for localizers time over the next two weeks.

Triage soon We'll use next weeks meeting slot to triage... no meeting, since we're freezing the project

Launch Date Grace would like to launch 1 week after Markup launches. Once we have TBG estimates, we'll see if this is possible. QA needs 10 days after blocking bugs are fixed.

Email Collection... how does that work? Claudia: Will ask brez - Email page collection - is it hooked up to Repsonsy ?


Next Actions

[] Claudia: Estimate amount of time TBG will be away until they can return to development on Webifyme.

[] ozten: Update schedule based on this estimate

[] Claudia: Estimate amount of time L10n blockers will take to fix

[] Claudia: Write up admin screen requirements

[] ozten: Give Krupa access to admin account on stage

[] William: Update copy bugs to be L10n blocker dependencies

[] Claudia: Will ask brez if Webifyme use Responsys for email address collection?

Next Meeting is probably May 11th