Mossop Status Update: 2010-06-14

Posted: June 14th, 2010

Done:

  • Got a bunch of bug fixes either done or ready for review
  • Started reviews for the component registration changes

Next:

  • Fixes fixes fixes
  • Triage for beta 2
  • Work out which of the big 3 impossible things is actually going to make Firefox 4

Tags: , ,

1 Comment »

Categories: mozilla

Mossop Status Update: 2010-06-04

Posted: June 4th, 2010

Done:

Next:

  • Fix bugs damnit
  • Update mobile to use the new AddonRepository.jsm that Ben has been working on

Tags: , ,

1 Comment »

Categories: mozilla

Mossop Status Update: 2010-05-24

Posted: May 24th, 2010

Done:

  • Triaged all the bug reports from the new add-ons manager to determine the list of blockers
  • Reviewing update tests

Next:

  • Complete the review of the update tests stuff
  • Fix a lot of the blockers in the new add-ons manager backend

Tags: , ,

No Comments »

Categories: mozilla

Where is the updated Nightly Tester Tools?

Posted: May 17th, 2010

Many of you nightly testers may have noticed that Nightly Tester Tools’ compatibility override feature doesn’t work with the new add-ons manager and may be wondering when I’m planning to issue an update to fix that. The more astute of you may have noticed that there hasn’t actually been a real code update to Nightly Tester Tools in 2 years, barring a couple of simple app compatibility fixes. Those with a sharp memory will remember that I said just under 2 years ago that I was ceasing work on my extensions in my spare time. I suggested that Nightly Tester Tools might still receive the odd update but obviously that hasn’t happened and the truth is that I can’t see it happening anytime soon. I’m too busy with that whole real life thing to even be able to work on projects I do enjoy, let alone maintain old stuff that no longer really interests me.

This unfortunately leaves a sizable number of users losing a feature that they liked and still potentially have a need for. I can only really see a couple of possible roads to follow from here:

  1. Do nothing. Users will be annoyed for a time but eventually find ways around what they needed NTT for.
  2. Find someone else to pick up and maintain NTT. I’ve had numerous requests for the source code for many of my extensions over the past two years, none have ever apparently tried to do anything though. Perhaps someone out there will pick up the torch this time?
  3. Point all the users to something else, like the Add-on Compatibility Reporter (once that is updated to work on trunk). While nothing else I know of works quite like NTT at least something is better than nothing, and ACR has the benefit of being Mozilla supported, provides Mozilla with valuable information about add-on compatibility and may be rolled into Firefox at some point.

Option 3 is the only one available that involves any work on my part but probably the choice that leads to less user annoyance, unless someone reading this wants to take up the challenge or has a better idea?

Tags: , , , , ,

6 Comments »

Categories: extensions

Mossop Status Update: 2010-05-14

Posted: May 14th, 2010

Done:

  • Relanded the new extension manager
  • Working through more bugs and issues
  • Started implementing transactions and locking for the main database

Next:

  • Fix overlays for about: urls
  • Make chrome registration possible for bootstrapped add-ons
  • Work on shipping default extensions with the app
  • Help Ben Parr, the new intern get up to speed

Tags: , ,

1 Comment »

Categories: mozilla

Add-ons manager re-landed

Posted: May 10th, 2010

A little sort of coincidental performance regression forced us to back out the new add-ons manager last week. It has now been re-landed with added bug fixes and should be in tomorrow’s nightly.

Tags: , , , , ,

2 Comments »

Categories: mozilla

Mossop Status Update: 2010-05-07

Posted: May 7th, 2010

Done:

  • Backed out the new extension manager
  • Fixed some of the bugs found during the extension manager testday
  • Found the cause of the Ts regression
  • Prepared everything to be landed again

Next:

  • Work out when we can re-land the new extension manager
  • Start churning through more of the known issues

Coordination:

Need to work with IT and RelEng to find out what the situation is with getting the Talos boxes all dongled up

Tags: , ,

No Comments »

Categories: mozilla

Mossop Status Update: 2010-04-30

Posted: April 30th, 2010

Done:

  • Landed the new extension manager

Next:

  • Tracking down a Ts regression from the new extension manager
  • Resolving any important issues that users and developers find from the landing

Tags: , ,

1 Comment »

Categories: mozilla

Mossop Status Update: 2010-04-12

Posted: April 12th, 2010

Done:

  • Worked on more review comments for the add-ons manager rewrite
  • Investigated a new issue that QA came across in the rewrite
  • Met with UX to talk about the Home Tab plans
  • Started playing around with building Firefox for the Palm Pre

Next:

  • Blog about the new restartless add-ons spec
  • Land the extension manager rewrite on trunk
  • Look at starting on the Home Tab project

Tags: , ,

1 Comment »

Categories: mozilla

Mossop Status Update: 2010-04-02

Posted: April 2nd, 2010

Done:

  • All major issues taken care of
  • Ported all the currently applicable tests from the old xpcshell suite to the new API
  • Finalized spec for restartless extensions

Next:

  • Address the next round of review comments
  • Land this sucker
  • Sleep

Tags: , ,

1 Comment »

Categories: mozilla