Mossop Status Update: 2011-04-29

Done:

  • Tidying up the loose ends of things still in progress
  • Cleaned out my review queue
  • Work on simulating nsIFile enough to emulate filesystem failures while installing add-ons (bug 653835)
  • Trying to test some weird edgecases for softblocking (bug 648599)
  • Fixing some issues with page history when custom add-on types are removed (bug 595848)
  • Trying to figure out how to manage my time better (again)

Next:

Mossop Status Update: 2011-03-25

Done:

  • Landed some fixes for Firefox 5
  • Improvements to the custom protocol to make displays nicer
  • Updating the patch to extend the add-ons manager, mostly complete
  • Replacement compatibility wizard is near complete

Next:

  • Sort out a list of high impact yet low risk things that we can take for Firefox 5
  • Land the patch for extending the add-ons manager
  • Get the compatibility wizard ready for review
  • Get the new protocol handler in some sort of feedback-ready state

Mossop Status Update: 2011-03-18

Done:

  • Prototype patch for simplifying extending the add-ons manager (bug 595848)
  • Thought about a plan for using a custom protocol for in-content UI (http://bit.ly/eRnDvm)
  • Working on the replacement for the extension compatibility wizard on app upgrade (http://mzl.la/hEmRv1)
  • Figured out the issue with fonts on some Galaxy S Froyo devices and made a couple of potential fixes (bug 636042)

Next:

  • Complete tests and all basic functionality for the compatibility wizard replacement
  • Finish the patch for extending the add-ons manager
  • Figure out whether a custom protocol is actually a good idea

Mossop Status Update: 2011-03-11

Done:

Next:

Getting the important projects up and running in time for Firefox 5.

What’s next for the Add-ons Manager?

Firefox 4 is just around the corner and it’s great to look back over just how far the Add-ons Manager has come since Firefox 3.6. In fact if you want to see the full history look at my earlier post that shows its evolution since Phoenix 0.2. We set out with some pretty lofty goals for Firefox 4 and I’m pretty excited at just how many of them we achieved. I hope everyone appreciates the hard work that Blair, Boriss, Justin, Henrik, Ben, myself and all the others put in to get us to where we are today.

Of course, we aren’t finished. There were a lot of things that we wanted to get done and didn’t get time for and I’m sure we’ll be getting lots of feedback from users of the final release to work on. Since the pressure has been off I’ve been skimming back over bug reports and notes to try to come up with an idea of what we want to work on over the next few releases of Firefox. As you may know the plan is to move to quarterly releases and not really block a release on any particular projects but we will still be getting an idea of what product drivers will prioritise work on and guess at what other things we can fit in.

UI refinements

In the closing stages of Firefox 4 there were a lot of small polish issues identified. We knocked down a lot of them but there are still plenty of tweaks that we’re going to be bringing to the UI to make sure it is as usable as we can make it. It isn’t really worth applying a fixed schedule to these as they are small one-off fixes that can just come as and when ready. We already have some that are basically ready to land.

Incremental API fixes

There are lots of things that I’d like to see done for the platform and APIs that developers use. Again there is no fixed schedule for these but the main things on my mind are changes that make developing restartless add-ons or extending the add-ons manager easier. I’ve already started work on a couple of these and expect to get them landed after the tree reopens.

Larger projects

There are of course also larger projects that will require more resources. I’ve started writing up short project pages for each of these. Each project should start with the people working on it coming to agreement on what the actual goals should be and an implementation plan so until the projects are actually picked up the project pages are mostly made up. I’ve put down a rough idea of when a project might make it into a Firefox release. These are just guesses, if the project turns out to be larger than expected they’ll come later, if people volunteer to work on projects or if the product drivers decide they are a priority then they could come sooner.

You can see that assuming a quarterly release schedule we have enough projects here to last till the end of 2011 at least, quite likely longer. Over that sort of time I guess it’s almost guaranteed that priorities and plans will change in the meantime but hopefully this gives an idea of what our thinking is at the moment. Expect to see progress on some of the things at the top of the list very soon!