Support/SUMOdev Meeting Notepad/2010 Q2

From MozillaWiki
Jump to navigation Jump to search

4 May 2010

Kitsune

  • 2.0(.1) m
    • Meeting in 45 minutes with IT to make sure everything's ready for Thursday.
    • Finalize database conversion process with Tim. (Paul and/or James)
    • Still need to load test, need help from oremj or clouserw with log_replay. (James)
    • QA: Any reservations or are we go? Readiness meeting? (Stephen)
  • 2.1 m
    • Filed lots of smaller, more manageable bugs.
    • Roll up your sleeves, let's get into it.
    • Target: all non-moderator functionality by end of week.

TikiWiki

  • 1.5.4 m
    • Only open bug is for Tim. We can't find the source of the issue, so we can probably just push it out.
  • 1.5.5 m
    • Will have a few small bugs to file this week. (James)
    • Once we have a schema in place from 2.1, will need to migrate data to it.
    • To nominate for 1.5.5, please put 1.5.5? in the whiteboard. Please only file regressions directly into 1.5.5 (ie: should have the regression keyword).

Chat

  • Status update from Matthew and Sam.

Roundtable

  • Yes, we are getting more developers.
    • Two FTEs and an intern starting over the next 4-6 weeks.
    • This is wonderful.
    • Really, it's awesome.
    • It will impact our engineering plan for this quarter.
  • I'm working with Morgamic to create an engineering plan for the next 3-4 months that will take advantage of these new resources.


27 April 2010

Web dev on-site this week. Progress will be slower than normal, and meetings will be higher than normal.

Kitsune

  • SUMO 2.0 froze on Thursday!
    • QA found a few things after the freeze.
    • We've fixed them.
    • Began work on 2.1, discussion forums.
  • There is now a Support Mozilla component on Verbatim.
    • It's not entirely accurate. It needs to pull new data.
  • Action items:
    • Get together with IT to discuss deployment (James, possible AMO friends).
    • Load testing (James and Paul).
    • Can we run one more database conversion test with the outage page up? (On support-stage.) (Paul, Tim Ellis)
    • Get Verbatim synced up (James, Gandalf).
    • Start iterating on the discussion forum branch.

TikiWiki

  • 1.5.4 needs our attention this week.
    • If you have bugs in this milestone, they are your top priority right now.
    • Freeze by Thursday at the latest.
    • Only demonstrable regressions should go into 1.5.4 right now. Please nominate with 1.5.4? in the whiteboard.
    • Anything else is 1.5.5 at the earliest. Please nominate with 1.5.5? in the whiteboard.
    • Can bug 561824 wait until 1.5.5?
  • Emergency tag.
    • We are making irreversible changes to the database. We should create a 1.5.3.1(ish) tag we can roll back to with only the SET NAMES patch from bug 554210.
  • Action items:
    • Finish/land all 1.5.4 work (James, Paul, Kadir, Matthew).
    • Create emergency tag (James).

Live Chat

  • Sam's here.
  • We should minimize the work done on TikiWiki.
  • Potential implementation:
    • JavaScript web client, that talks to a
    • Python/Django intermediary (Django "livechat" app), which then communicates over
    • XMPP with the chat server.
  • Action items:
    • Nail down the goals (Sam, Matthew).
    • Implementation plan (Sam, Matthew).
    • Get started! ;)

Roundtable

20 April 2010

Kitsune

  • Put out several fires yesterday. Interfered with work getting done.
  • Obviously missed freeze on Friday.
  • QA: Still need to run our Latin1 -> UTF-8 script on support-stage-new.
  • New dates?
  • Pre-push work:
    • Testing.
    • Load testing. Will file relevant IT bugs after meeting.
    • Verbatim. Will ping relevant people after meeting.
  • 100% of our focus right now is on finishing this out.

Live Chat

Roundtable

13 April 2010

Continuous Integration

  • We've got Hudson running our Kitsune unit test suite after every check-in!
  • We're at ~80% coverage right now.
    • The Sphinx API is currently a large percentage of our code and we aren't aiming for 100% there, so until we find a way to exclude it, it will skew coverage reports downward.
    • Feel free to add tests to improve coverage. These branches don't need a bug but do need review.
  • We need to work out what, if any, useful information we can get from pylint.

Kitsune - 2.0

  • 13 open bugs
  • Still trying to freeze on Friday—that makes this an intense week. Focus on blockers, then other P1s, etc.
  • Please start testing now.
  • Need to get in touch with localizers (see bug 557574).
  • Note the new coding standard for templates: indent with two spaces, and include a modeline at the top of the file:
{# vim: set ts=2 et sts=2 sw=2: #}

TikiWiki - 1.5.4

  • 8 bugs
  • Aim to freeze on... Tuesday?
  • Mostly small/simple tweaks or issues.
  • If you have anything else urgent, please nominate ASAP (with 1.5.4? in the white board and a good reason in the comments).

Releases

  • When should we look at pushing Kitsune?
    • Need to start talks with IT about requirements and deployment process.
  • QA has suggested readiness meetings.

Roundtable

  • Forum rewrite status

6 April 2010

First SUMOdev meeting of Q2!

Kitsune

  • 15 open bugs :/
    • Mostly low priority (7) or in review queues (3) or don't specifically require work (2).
  • Biggest blockers are sessions and character encoding.
  • Still aiming to freeze 16 April.

1.5.4

  • Nothing nominated.
  • 4 bugs
    • Will start directing searches to Kitsune.
    • Mobile branch is still closed until 1.5.3 push.
    • Still aiming to freeze on 16 April.
Retrieved from "https://wiki.allizom.org/index.php?title=Support/SUMOdev_Meeting_Notepad/2010_Q2&oldid=220242"