Comment 5 for bug 488967

I think I read somewhere in the Tracker changelogs that they committed a fix for this, but maybe I mistook a normal comment on the matter as a real committed fix...

Regarding 0.3 status I think we should ship 0.3.0 without it. There's nothing stopping us having 0.3.1 next week already of we have good features and fixes lined up. It's just to make sure that we in fact get *something* out there. We are in danger of ending in perpetual-feature-creep lan otherwise...

As I also stated to Seif I'd rather delay this a bit until we've figured out a good API, than ship something we have to change shortly after.