Support/SUMOdev Meeting Notepad: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 29: Line 29:
*1.4.1 [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+product%3Asupport+milestone%3A1.4.1 bugs] regressions ([https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=support&field1-0-0=target_milestone&type1-0-0=substring&value1-0-0=1.4.1 open bugs])
*1.4.1 [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+product%3Asupport+milestone%3A1.4.1 bugs] regressions ([https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=support&field1-0-0=target_milestone&type1-0-0=substring&value1-0-0=1.4.1 open bugs])
**Freeze October 15
**Freeze October 15
**Push October 20
**Push October 22
*Fennec timeline:
*Fennec timeline:
**Aug 27 Freeze 1.3
**Aug 27 Freeze 1.3

Revision as of 20:53, 13 October 2009

Tuesday (meeting duration approx. 30-45 minutes) at:

  • 9:00 AM PDT
  • 12:00 PM EDT
  • 18:00 CEST

Phone call details:

  • California: 650-903-0800 then extension 92
  • Toronto: 416-848-3114 then extension 92
  • Toll-free: 800-707-2533 then password 369
  • Skype (free): +18007072533 then password 369

Then, enter the conference number: 309#

Please mute your microphone as long as you are not saying anything to prevent feedback and other noise in the conference. Thank you!

irc.mozilla.org: #sumodev

More about SUMOdev

Next releases

  • 1.5 bugs Search
    • Freeze November 24 (provisional)
    • Push December 1 (provisional)
  • 1.4.2 bugs UX and high priority changes
    • Freeze October 29
    • Push November 3
  • 1.4.1 bugs regressions (open bugs)
    • Freeze October 15
    • Push October 22
  • Fennec timeline:
    • Aug 27 Freeze 1.3
    • Aug 28 - Sept 3 QA
    • Sept 3 - Tag 1.3 branch Fennec
    • Sept 10 - Retag, rebranch, push 1.3
    • Sept 4-8 Make Fennec template and SHOWFOR changes
    • Week of Sept 8 have staging server up for Fennec team feedback (
    • Week of Sept 14 (dependent on IT delivery of bug 511423) get prod up for Fennec team to work on articles
    • Week of September 28 - ship it!

October 13

  • 1.4.1 status (as of Oct 12):
    • 38 bugs verified.
    • 9 bugs fixed waiting for verification.
    • 12 open bugs - 4 web dev, 7 chat, 1 tracker.
    • Bugs to discuss:
  • 1.4.2 status (as of Oct 12):
    • 22 open bugs.
    • 10 have patches for review.
    • Let's hold this to 25 bugs or less--not counting chat--we're in good shape right now.
    • Bugs to discuss:
  • 1.5 status:
    • Onsite for Sphinx is today (Oct 13)
    • Still need to either batch move bugs to 1.6 or work some bugzilla ninjary.
    • Will open a branch when we open 1.4.2
  • Status of Tiki upstream goals?
    • LPH could start this week, based on my chat with him a few weeks ago (djst)
  • Having a meeting to discuss Live Chat login integration (bug 453058)

October 6

October 1

  • Triage bugs pushed out of 1.4 into 1.4.1, 1.4.2, and 1.5

September 29

  • Webclient status [zzxc]
  • Fennec going into prod *tonight* - Paul to update install instructions for IT. Latest is that we will copy staging db to prod. bug 519449
    • Should forums be enabled? -cilias
    • Should translating be possible? -cilias
  • 1.4.0.1 on Thursday - push bug needed
  • Q4 goals
  • Take a closer look at bugs - Milos

September 22

  • 1.4 status
    • AAQ
    • Release will push Thursday
    • Webclient [zzxc]
  • JS policy for contributors [1] -cilias
  • SUMO future matrix status [jsocol, laura]
  • Fennec status

September 15

  • 1.3.0.1 - did this go out?
  • 1.4 - I'd like to freeze Thursday - could we still push Tuesday, QA?
  • Fennec: waiting on staging site, some emails back and forth.
  • Upgrade matrix status [jsocol]


September 8

  • 1.3
  • 1.4

September 1

  • QA status on 1.3 [stephend]
    • Regressions bug 513840 and other problems bug 487598
    • Branch management: do not merge 1.4 bugs to trunk until 1.3 is tagged
  • 1.4 bug overview
    • long triage yesterday, note bug importance and priorities when planning work
  • Support/TikiWikiUpgrade - contributions welcome

August 25

  • Guest calling in today: Marc Laporte from TikiWiki
  • p12n triage and review - are we still on track for Thursday?
  • Fennec timeline (look up)
  • 1.4 status (briefly - we'll focus on this next week)
  • Roundtable

August 18

  • p10n status
  • Forum UX status
  • Web client status
  • Roundtable

August 11

  • Welcome to jsocol, joining the team as a full time webdev
  • p10n and 1.3 general status
    • Focus has to be on p10n bugs before anything else
    • Help for ecooper - paulc, jsocol
    • Freetags bug 473000 -- best approach? [paulc]
  • Metrics update [Cww]
  • 1.4 status
  • Roundtable
    • [paulc] Call community for list of features used on SUMO

August 4

  • p10n status
    • Templates - what is needed?
    • Staging server
  • 1.4 status
  • Roundtable

July 28

  • 1.2.1 status, notes about freeze
    • Can we push this out tonight? stephend?
  • 1.3 status
  • 1.4 status
  • Roundtable

July 21

  • 1.2.1 status
  • P10n
  • Forum UX
  • Kampyle stuff

July 14

  • Search issue solved (thanks Eric) - mini push tonight
  • P10n status [ecooper]
  • Forum UX status [paulc]
  • 1.2.0.1 no news
  • Roundtable

July 7

  • Release timeline for Q3 (see above)
    • Productization work not publicly visible, do in trunk
    • Maintenance release in trunk
    • Forum UX needs a branch (add in branches/forumux)
    • Webclient timeline? Needs branch
  • May do small release (1 line) Thursday to tweak Kampyle
  • Status roundtable

June 23

  • 1.2 open bugs
    • Aim to push Thursday dependent on IT and QA
  • Q3 goals
    • Productize SUMO - Make SUMO a support solution that can be deployed for other software projects
    • Launch SUMO powered Fennec Support website
    • Improve UX of Support Forum -- see PRD for details: https://wiki.mozilla.org/Support/ForumUX/PRD
    • Implement web-based Live Chat client

June 16

  • A/B test status
  • 1.2 status
  • Q3 goals

June 9 2009

  • Screencasts status - are we on track to release tonight? [stephend]
  • Kampyle survey bug 496967 - can we do this for tonight or hold off? 1.1.1 or 1.2? [all]
  • Metrics dashboard - above dates still ok? [paulc]
  • Major triage effort this week
  • Q3 goals - will discuss next week
  • Laura in MV next week

June 2 2009

  • 1.1 in QA - questions, issues, problems, status?
    • Push next Tuesday.
    • A/B test stuff will need to go out with 1.1
  • Depending on RC1 timeline we may do 1.0.4 on Thursday - release management only required, no code changes (just adding patches to 1.0.3).
  • 1.2 - metrics dashboard demo [paulc]
  • Roundtable

May 26 2009

  • Status of 1.1 [laura, all]
    • In patch review - try to post patches *before* freeze day
    • Merge 1.1 and 1.1.1 releases - propose freeze Thur, push Tue
  • A/B tests status [paulc, djst]
  • Metrics dashboard status [Cww, paulc]
  • Roundtable

May 19 2009

  • Congrats on 1.0.2 :)
    • Postmortem this week sometime
  • Where are we with screencasts?
  • Metrics status (need meeting - tomorrow?)
  • A/B tests status
  • Roundtable

May 12 2009

  • Enabling new search today!!!!!11!!eleven
  • Screencast status
    • Can we still freeze tonight - not quite ready, freeze Thursday.
    • 1.1 bug review - should be ok.
  • Start Page Optimization A/B test
    • prod files sent to paulc (preview), too big to add to bug
    • Let's figure out timeline
  • Metrics dashboard status

May 5 2009

  • 1.0.2 - can we freeze today?
  • Screencasts status- ecooper out of town until Thur but on track.
  • Metrics - discussion of task allocation between SUMO team and metrics team
  • Roundtable

April 21 2009

  • Still quite a few search bugs (stephend)
  • Non-search 1.0.2 bugs still open
  • Screencasts

April 14 2009

April 7 2009

  • 1.0.1 status
  • Dates for next releases
  • Plan for search - bugs in 1.0.2? Do we need more functional testing?
  • Support/1.0_Postmortem
  • Roundtable

March 31 2009

  • Releases:
    • 1.0 goes out tonight, along with the database upgrade
    • 1.0.1 only exists to make changes from 3.1 to 3.5.
    • 1.0.2 is the next proper release
  • Goals for Q2 [djst]
    • Implement screencast support
    • Automatic metrics dashboard
    • Conduct A/B tests with redesigned SUMO start page to evaluate best ways to lower the bounce rate
    • Proof-of-concept web-based Live Chat client (zzxc)
  • Date and time for postmortem?

March 24 2009

  • Version numbering change.
  • 0.9.5 will go out tonight.
  • Freeze for 1.0 has been pushed back to Thursday, so we can get any last fixes in.
  • Also on Thursday, SUMO databases will be upgraded to a better database cluster, which should solve a lot of our current performance issues (timeouts, forum posting problems, database crashes, etc)
  • 1.0 will go out next Tuesday
  • l10n dashboard will go out in 1.0. This is our number one priority.
  • Review of remaining search bugs - can we get these in for 1.0 (P2)?
  • Please add SQL changes needed for 0.9.5 to the push bug
  • Requirements for Live Chat webclient

March 17 2009

  • l10n/1.0 status
  • UX/1.1 status
  • Search
  • Roundtable

March 10 2009

  • Laura on vacation this week
  • l10n dashboard status
  • UX/1.1 release status
  • ecooper and stephend tested the watch-list functionality, and it didn't work 100%; ecooper to add debugging calls to tiki-editpage.php to see if stephend's test account email is being included in the outbound email notification list
  • roundtable

March 3 2009

  • 1.0 l10n release triage
  • load test status [laura]
  • UX review status [neilio]
  • Laura on vacation next week

February 23 2009

  • 0.9 blocker
  • Remainder of 0.9 bugs
  • Dates for 1.0 and 1.1

February 17 2009

  • Release status
  • l10n [djst]

February 10 2009

  • Search status
  • l10n release plans [djst]
    • Ability to prioritize list of en-US articles -- using tracker db? suggestion by Marc Laporte
    • We would then develop a function that would get the status of an article:
      • Short term: translated, not translated, waiting for review
      • Long term: % of up-to-dateness, not translated, waiting for review
    • Show this on contributor home page (or link to it) in a nice looking table, with status field and action links like "translate article"
    • Also wanted: list of articles waiting for review for current locale (show on contributor home page for reviewers)
  • 0.9 triage
  • Roundtable

February 3 2009

  • Search status
  • 0.8.2 and 0.9 -> combine?
    • Outcome: whatever is committed today will push Thursday as 0.8.2, all else goes to 0.9 on the existing schedule
  • l10n release plans [djst]
  • Roundtable

January 27 2009

  • 0.8.1 push follow ups
  • 0.8.2 status
  • Search load test report (Nelson)
  • Roundtable

January 20 2009

  • 1.0 will now be l10n and 1.1 will be UX
  • 0.8.1 going out tonight, please check the push bug bug 472317
  • Dates for 0.8.2, 0.9

January 13 2009

January 6 2009

  • Happy New Year!
  • Status of each person's bugs for 0.8.1 (including status of search)
  • Roundtable

December 30 2008

December 23 2008

December 16 2008

  • 0.8 status
  • Future release planning: short 0.8.1, mostly for sec bugs?
  • Next week's meeting: review 2008
  • Roundtable

December 10 2008

  • 0.8 status
  • Load test status - this will block release, waiting on advice from IT
  • Yet more security bugs

December 2 2008

  • 0.7.3 goes out tonight
  • Search status
  • CSAT status (Live chat)
  • Security bugs
  • Screencasts
  • 0.8 triage

November 18 2008

  • Screencast/Mogulus discussion
  • Regressions:
    • The "No screenshot" issue -- discussion about what happened, how we can avoid similar things in the future, and whether or not we should avoid pushes close to a Firefox release bug 464913
    • Other regression, re new sanitization: bug 465530. This is a blocker. Prefer off schedule push, or revert?
  • Search status
  • Live Chat CSAT status
  • I haven't yet looked at search on support-stage at all; anybody else? Sorry, been swamped with Bandwagon -- stephend
  • 0.7.3 triage
  • Roundtable

November 11 2008

  • 0.7.2 status
  • Goals status
  • Review dates for 0.7.3 and 0.8

November 4 2008

October 28 2008

  • 0.7.2 freeze *Tuesday* November 4.
  • Roundtable

October 21 2008

  • Welcome to Paul Craciuniou!
  • 0.7.1 goes out tonight.
  • Search engine status (Nelson)
  • CSAT forum status (Eric)
  • Live Chat status (Matthew)
  • 0.7.2 triage. Other bugs for nomination?
  • 0.7.2 freeze is Thursday November 4th

October 14 2008

October 9 2008

  • Proposed dates for Q4.
    • 0.7.1 freeze Thursday 16th Oct, push Tuesday 21 Oct
    • 0.7.2 freeze Tuesday 4th November, push Thursday 6th Nov
    • 0.7.3 freeze Thursday 20th Nov, push Tuesday 25 Nov
    • 0.8 freeze Tuesday 9th Dec, push Tuesday 16 Dec
  • djst and laura in process of triage for all Q4 bugs(!)
  • New team member Paul C (will hopefully join call next week)
  • Discussion of comment search and archive policy
  • Roundtable


September 30 2008

  • 0.7 push tonight
  • Goals for q4:
    • Deploy improved search engine to replace Google
    • Implement CSAT for the Support Forum and Live Chat
    • Define infrastructure and UI PRD for screencast support
    • Improve ySlow scores (pushed out from q3)
    • Implement performance metrics for the support forum (add 'solution to prolem proposed' status to forum threads)
  • Roundtable

September 23 2008

  • CSAT status
  • Email notifications
  • 0.7
  • Freeze THURSDAY AT 11.59 PDT.

September 16 2008

  • Push tonight, bug is https://bugzilla.mozilla.org/show_bug.cgi?id=455344
  • CSAT status - nkoth, jwaller, zzxc
  • Email notifications status - lorchard
  • 0.7 - other bugs. Suggest we realistically reduce to just the above + any security or other critical performance issues - laura
  • Code freeze for 0.7 is Thursday 25th September, release Tuesday 30th September.


September 9 2008

  • CSAT progress
  • Email notifications
  • Code freeze for 0.6.4 scheduled this Thursday - looking ok [2]

September 4 2008

August 28 2008

  • Introduction to John
  • Code freeze 0.6.3 scheduled today - push out?
  • Discussion of search, see bug 443944
  • Customer satisfaction metrics for the KB for 0.7 -- plan?
  • Need more memory on LiveChat server - still getting OOM errors
  • Roundtable

August 19 2008

  • Welcome back and update for our glorious leader
  • 0.6.2 ([3]) will go out tonight (bug 451055
  • What bugs for 0.6.3? [4] Only 12 in there right now (See 0.7 for further candidates [5])
    • Code freeze 8/28, push 9/2
  • New contractor starting next week (John Waller)

August 12 2008

  • 0.6.2 freeze Thursday night (8-14, 11.59 PDT)
  • 0.6.2 triage [6]
  • Roundtable

August 5 2008

  • 0.6.1 was successfully pushed.
  • Set dates for 0.6.2 (Suggest freeze 8-12 or 8-14)
  • Live chat updates from Jive (XSS to be fixed in 3.5.3 < 1 month away, DOS issue will not be fixed).
  • 0.6.2 quick triage [7]
  • Updating TikiWiki to latest version, and merge stuff upstream [nelson]. Aiming for 0.7 and work will be done in https://svn.mozilla.org/projects/sumo/branches/tiki-upgrade/
  • Check Bugs between now and 0.7 to see what we're missing from the forum aspects of the SUMO vision document. Basically:
    • Email notifications, including links to yes, this answered my question and no, it didn't bug 444335
    • Offer various ways for users to keep track of their asked questions, e.g. an Add Bookmark button, an RSS feed, and the e-mail notification system described above. (Feeds in bug 422001, decided against bookmarks, too confusing for users.)
    • Support for forums in different languages. (What's needed here? Create a page of links to localized forums?)
    • Per-post connection to customer satisfaction, meaning the contributor providing the solution to the problem receives karma. (Karma system needs more thought before we can do this one. Tiki has a built in karma system that we should be able to reuse/bend to our needs.)
    • Provide clear, meaningful ways for contributors to filter forum posts based on status (unsolved, unanswered, etc) (bug 444331)

July 28 2008

  • No meeting due to Summit

July 21 2008

  • 0.6.1 triage and status
  • Security bug review
  • Roundtable

July 15 2008

  • 0.6.1 triage [[8]]
  • Scheduling:
    • Subject to IT's approval (due to Summit timing and travel):
    • Code freeze for 0.6.1: Thursday July 24th
    • Push for 0.6.1: Tuesday July 29th
    • We'll aim to be bi-weekly after this.
  • Roundtable

July 8 2008

  • Triage 0.6.1, 0.6.2, 0.7 and unassigned bugs.

July 1 2008

  • Open bugs for 0.6: [[9]]
  • Planned code freeze tonight at 11.59pm PDT: after this, no changes to production branch until we're tagged.
  • Between freeze and push, QA to verify remaining closed 0.6 bugs.
  • Push will occur Weds or Thurs night (dependent on IT)
  • Between now and next week: review bugs with Target "--" and see what else needs to go into 0.7. (Theme for 0.7 is forum improvements.)
  • Any other items?
Retrieved from "https://wiki.mozilla.org/index.php?title=Support/SUMOdev_Meeting_Notepad&oldid=175401"