Mozilla Webdev

The Socorro database, which is the main database for Firefox 3 crashes, will be going through some maintenance upgrades this week. Starting tonight, this means:

• Report data prior to June 23rd will be temporarily unavailable.
• New reports will work as usual on our new database.
• Old data will be imported into the new database using an improved partitioning plan.

Reasons why we need to do this now:

• Firefox 3 crash throughput has been about triple the projected amount (due to the popularity of Firefox 3).
• The current database has a partition that is unmanageable without significant downtime (2-3 days)
• The Socorro reporter is not responsive because of the size of the current partition.

No individual reports will be lost, they will be restored over the next week. Please let us know if you have any questions.

Les came up with a way to syndicate the Download Day JSON feed. You might want to check it out.

Last week we had our entire team on-site and had discussions about where we’ve been and where we’re headed. I put together a short presentation about past, present and future then we had a short brainstorm session about “ok, what’s next?”.

We wanted to share all of this with you to invite any additional feedback or ideas for how we can make the Mozilla web better. Below are the notes from our brainstorm session, and I invite you to add to the wiki page or comment here.

Our main questions for the future that we’d like your thoughts on are:

• What would you like to change about our websites?
• How do we encourage more community participation in development?
• Give us a project idea!

Again, check out our brainstorm notes and we’d like to hear from you if you have any ideas to add to this list! Thanks.

We attempted to push the AMO 3.4.3 update last night but ran into some problems. Our initial investigation is pointing to the advanced search queries taking far longer than the previous version. The slave databases couldn’t handle the load and we had to back the update out. We’ll come up with a solution this weekend and plan on pushing the 3.4.3 update on June 12th.