1. The server-side components (bug reporter, command search engine,
etc) are not anywhere near ready. I've been working on them all day
and discovered that the job is much, much bigger than I thought. I
thought it was going to be a one-day thing but it looks more like we
will have to seriously rethink the server infrastructure if we want to
offer bug reporting and command search services to our users.
2. Support: After we release 0.5 onto addons.mozilla.com, since it is
such a big change to how ubiquity works, there is bound to be a huge
influx of users with support requests, maybe more serious bugs
discovered, etc. This would be happening while I was gone and not
able to help with any of the support work. Leaving the users hanging
with new problems due to 0.5 might be a worse thing to do to them than
making them wait another couple of weeks to get 0.5.
3. Features: If we push it back, we will have time to try to put in
some of the features we cut out: Suggestion memory, provider-plugin
arguments, and most of all, asynchronous noun-first suggestion (in a
way that doesn't count as a DDOS attack on Yelp).
So, if we push it back, then we'll be able to do a more polished
release, with the server-side components working, and at a time when
I'll be available to help with the support and bug fixing and the
inevitable patches that will be needed.
This isn't just my decision, though. What does everybody else think
of pushing the release back?
1. if we push it back we will be letting down all the people who have
already blogged/written/read about the 0.5 release
2. the XPI itself is ready
3. The server components are not ready, but 0.5 without bug reporter /
herd is at least not any worse than 0.1.8 without bug reporter/herd
4. The rest of the community can handle support without me ;-)
5. Getting people onto 0.5 will reduce the load on the ubiquity.mozilla.com.
We should replace the herd and bug reporter pages with notifications
that tell users those services are down for repair, and then focus on
getting them working after the 0.5 release is out.
Atul and Aza have agreed to manage the release while I'm gone.
I think Tuesday is a good day ;D
Btw, i emailed the couchdb user-list, but i really need the logs from
the server (so they can say what's going on).
Also, i prototyped another bug-report app , using MongoDB  - if
we can't make couchdb work, i think this is a good replacement.
On Jul 4, 2009, at 6:47 PM, Zach wrote:
> What about folding the Ubiquity commands into the pre-existing add-ons
> site? Can we bring SUMO on board to get the documentation up to
> snuff? That would get us back on track much more quickly- and it's
> what is going to happen sometime down the line anyway.
> Wasn't there a plan to get someone working on the HERD full time for
> the summer- an intern or something...
> On Jul 3, 8:38 pm, "mitcho (Michael 芳貴 Erlewine)"
>> Jono, this sounds great. The server-side is definitely a priority
>> worth seriously working on in the near future. Looking forward to
>> seeing you on Monday! :D
>> I will email ubiquity-i18n about the localization time schedule. I
>> personally think the more public outreach to the broader localization
>> community (through dev-l10n), especially given the limited time until
>> next Tuesday, is better suited to right after the 0.5 release.
>>> Hey everybody,
>>> I apologize for my panicky email on Thursday afternoon; I was very
>>> frustrated at my inability to get the server-side components
>>> and I got pretty emotional (as those who have to share an office
>>> me can attest). Anyway, after hearing from everyone about it, I
>>> we are good to launch early Tuesday morning.
>>> Today I pushed a 0.5pre4 (up on the site now). It includes
>>> changes to
>>> the web content and the Report Bug command, so that users who are
>>> looking to report bugs are directed to Get Satisfaction, and users
>>> looking for more commands are directed to the Commands In The Wild
>>> wiki page. I think both of these will be more helpful than
>>> them to non-functional Herd and Bug Reporter services.
>>> I think 0.5pre4 is ready to be renamed 0.5.0 and released, but it
>>> should be stress-tested by everyone involved to make sure it can
>>> upgrade cleanly, that it has decent performance and generates
>>> reasonable suggestions, and that the tutorial works.
>>> The Herd and the report-bug service will likely require a complete
>>> rewrite of the backend infrastructure before they are functional.
>>> They both depend on a single couchdb install which currently
>>> stands at
>>> 6 GB, and which cannot run for more than a few minutes without
>>> crashing. I was unable to get it to stay up for any length of
>>> even after spending most of yesterday on it. So I think we'll
>>> need to
>>> start some new server infrastructure from scratch in order to
>>> Herd and the bug reporter the way we want to. That should be one of
>>> the main priorities after we release 0.5.0.
>>> As I said, I think we're good to release Tuesday morning. I agree
>>> with Christian about pushing to get translations done for that.
>>> Please, no new features or functional changes: just translations,
>>> testing, and bug fixes.
>>> Aza has agreed to take responsibility while I'm gone, to write the
>>> release blog post for 0.5 and to manage the release of any dot-
>>> that are afterwards found to be neccessary (0.5.1 etc).
>>> I am leaving on my trip tomorrow morning, so I can do no more on
>>> release. The rest of you will have to decide the exact timing of
>>> 0.5.0 release, and manage its execution.
>>> Good luck!