QA/Execution/Web Testing/Meetings/2011-06-18: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
No edit summary
 
(11 intermediate revisions by 4 users not shown)
Line 4: Line 4:
* This should actually be under https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-06-17
* This should actually be under https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-06-17
** Honey badger don't care (*waves hands*)
** Honey badger don't care (*waves hands*)
* Verifying security bugs
* Work week - what are we doing?  (Have a look at the scrumpad)
**http://mozqa.sync.in/mozwebqa-work-week6-20-11
**Will also try to reserve Get to Da Choppa for the week


= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =


*AMO  
*AMO  
** [http://tinyurl.com/69q479y AMO 6.0.1] went live yesterday.
** We are doing another release this Tuesday for SDK pages
** [http://tinyurl.com/5tgxk4k AMO 6.0.2] is scheduled for 06/17
** Lots of pull requests merged for amo rewrite last week - yay!
** Created pivotal tracker with stories for amo rewrite
*Input
*Input
*Jetpack
*Jetpack
*Mark Up  
**Working on [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&classification=Server%20Software&query_format=advanced&bug_status=RESOLVED&component=Add-on%20Builder&target_milestone=Builder%200.9.6&product=addons.mozilla.org 0.9.6], which ships Tuesday
*Mozilla.com  
*Mark Up
** [https://markup.mozilla.org Shipped!]
*Mozilla.com
** Shipped [http://tinyurl.com/4xncdll resolved] bugs
** Shipped [http://tinyurl.com/4xncdll resolved] bugs
*Mozillians
*Mozillians
Line 17: Line 28:
*MDN
*MDN
** Shipped [http://bit.ly/mdn096 0.9.6] 6/16/2011
** Shipped [http://bit.ly/mdn096 0.9.6] 6/16/2011
*GetPersonas.com  
*GetPersonas.com
** [https://bugzilla.mozilla.org/show_bug.cgi?id=664328 Shipped] on 6/16
*Socorro
*Socorro
** [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&classification=Server%20Software&query_format=advanced&bug_status=RESOLVED&component=Socorro&target_milestone=1.9&product=Webtools 1.9] in progress
*Spark  
*Spark  
**No update
**No update
Line 26: Line 39:
** [[http://moxie.jamessocol.com/bugstats/sumo/2011-06-21 6/21]] coming up next Tuesday
** [[http://moxie.jamessocol.com/bugstats/sumo/2011-06-21 6/21]] coming up next Tuesday
*Webify Me
*Webify Me
**Couple QA-blocking bugs


= Time off / Out-of-office  =
= Time off / Out-of-office  =
* rbillings 6/17 OOO
* rbillings 6/17 OOO
* stephend gone 6/29-7/8 (parents + brother are in town)


= Takeaways and Action Items =
= Takeaways and Action Items =

Latest revision as of 18:19, 17 June 2011

previous mtg | QA/Execution/Web Testing/ Web QA Home | next mtg

Discussion Items / Updates

Project Status / goals for next week (keep it brief)

  • AMO
    • AMO 6.0.1 went live yesterday.
    • We are doing another release this Tuesday for SDK pages
    • AMO 6.0.2 is scheduled for 06/17
    • Lots of pull requests merged for amo rewrite last week - yay!
    • Created pivotal tracker with stories for amo rewrite
  • Input
  • Jetpack
    • Working on 0.9.6, which ships Tuesday
  • Mark Up
  • Mozilla.com
  • Mozillians
    • No update
  • MDN
  • GetPersonas.com
  • Socorro
    • 1.9 in progress
  • Spark
    • No update
  • SUMO
    • [6/14] SUMO release went out on....6/14!
    • [6/16] SUMO bonus release- delayed releasing HUGE translation change to allow for additional testing [not a regression/bug release]
    • [6/21] coming up next Tuesday
  • Webify Me
    • Couple QA-blocking bugs

Time off / Out-of-office

  • rbillings 6/17 OOO
  • stephend gone 6/29-7/8 (parents + brother are in town)

Takeaways and Action Items

(from last meeting)

  • Matt Evans to bring up a goal-writing workshop w/Debbie
  • Stephen to follow-up with Dave and David on load-testing w/user-interactions in Selenium 2 + the Selenium-running vendors
  • Stephen to follow-up with Matt Brandt and see what we can do with multi-node jmeter
  • Matt Brandt to work with the team and come up with a list of tests for Engagement projects we can automate