Pending submissions have all been processed. Thank you all for your submissions, and thanks to all our reviewers who helped us get our queue from more than 385 add-ons to 0 in the last few days. We’ve reached our goal, and will be working on migrating the entire add-ons database today.
We know everyone is anxious to get the developer control panel unlocked. Our schedule looks like this:
- March 5 – Migrate the add-ons database and update preview.addons.mozilla.org
- March 5-12 – Community testing of preview.addons.mozilla.org, ongoing bug fixing and polishing
- March 12-15 – Final bug fixes and adjustments based on community testing and feedback
- March 15 – Deployment of new addons.mozilla.org
You may have some questions. If you have any questions that aren’t addressed below, please leave a comment or find us in IRC. Here are some general FAQ:
- When will the developer control panel be unlocked? The developer control panel will be available from preview.addons.mozilla.org on or shortly after March 5, pending the database migration which has already started.
- Why is it taking so long to release the new site? We want to do what is best for our users. After our attempted release last month we realized we should slow down a bit and work with our community more to make sure the site is what everyone wants. We have already found and resolved a lot of bugs, and hope to find/resolve more to make the new site more robust.
- What do we do between now and March 15? We would like the community, including developers, to use preview.addons.mozilla.org to update their add-ons. We encourage everyone to add translations where possible and test the developer tools. We also need everyone’s help testing the public pages including reviews and discussions.
- How do you know that the site will work this time (on March 15)? After our last two attempts to switch over, we found two areas that were performance bottlenecks. One was a MySQL query for dynamic l10n data that was joining on a temp table, which means no use of indexing in MySQL. The other issue was the add-on model binding other db objects like previews unnecessarily, which caused cache entries to exceed their maximum allotted size due to series of preview images being pulled with normal add-on data. Both issues have been resolved and we have tested them using a new log replay script that we used to replay actual addons.mozilla.org traffic. The results were very positive and we have a much higher level of confidence.
- Where do we file a bug about the new site? If you find any bugs while using preview.addons.mozilla.org, you may file them here.
- What if we need to update something in the old database? If it is an emergency, please file an administration bug. In most cases, we will not update the old site and encourage you to update preview instead.
That’s it for now. Looking forward to a solid week of testing, and the launch shortly after. Thanks again for all of your help and support.