Websites/Markup/Meetings/2011-05-03

From MozillaWiki
Jump to: navigation, search

This the agenda and action items for the weekly check-in meeting for Markup, which took place on 2011-05-03 at 12:30am in All Your Base and Conference #329.

Agenda

GO!

The purpose of this meeting is to get a development status update, triage outstanding bugs and identify action items for Markup.

  • Identify Attendants and their Roles in this project.
    • Product owner - Laura
    • TPM - Ryan, Chris
    • Web Developer - Austin
    • IT - Corey
    • QA - Matt, Stephen
    • Security - MCoates
    • Legal -
    • L10N - Stas

Status Update

  • We are currently focused on shipping the product on May 10th.
  • Statuses
    • Laura
      • We are almost ready to go after a flurry of bug tickets
      • TBG has got the IE9 issues nearly resolved
      • The admin screen is not allowing her to log in when using Firefox.
      • Still has concerns on the super user needs.
      • Can we have influential people like Mitchell at the start of the stack?
    • QA
      • He needs to do some additional regression testing now that code code base is more stable.
      • There is questions around how the master and slave databases are going to function. The reads and the writes are going to be split off because of load balancing. The slave is in read-only mode.
    • IT
      • We are working into a shared stage environment so any blocking of databases for testing is going to effect other stage services. They want to move into a separate staging environment so they are able to test better.
      • Reviewing the databasing scheming and making sure there are no glaring issues.
    • L10N
      • On track and we should hit our goal of 5-10 languages
    • Web Dev
      • 3 bugs not assigned to people in target 1.0 milestone.
      • We could do a little testing in production -- dark launch.
      • Verified that the facebook bug is fixed.
    • Security
      • We are behind on the versions of django (1.2.3 and there were security fixes to django that have not been applied the to markup's platform. It may be difficult to upgrade to 1.2.5, but it they are not sure.
      • Admin screen is still buggy
  • Is the goal for shipping on May 10th on track, or is it at risk?

Notes

  • New launch date: May 17th

Bugs

Action Items

The following action items were outstanding from the previous meeting:

  • Laura: To ask TBG on why she is unable to log into the admin panel.
  • Laura: To ask TBG if they can upgrade the version of django to solve a known security issue.
  • Laura: Delete all of the existing marks, have the 3 important people put in their marks, and then we should be ready for the dark launch.
  • Austin: He is going to do a code review of models and multidb-router
  • CShields/Matt: Will decide if turning off the master DB to make sure it is able to read from the slave is worthwhile (would block other teams).
  • MCoates: He will look into if he feels that the upgrade to the latest version of django should be a blocker or not.
  • Austin: He will investigate what it will take to upgrade django, but it may invalidate any existing testing due to the system being upgrade. Will wait for MCoates bug before committing any changes.
  • Corey: To have a separate stage environment instead of the current shared hosting.

Next Meeting