In the interest of keeping users informed and hopefully involved, I’d like to let people know what we’re planning on doing in the next couple of Camino releases.
Addressing the most commonly asked question first, there are no plans to include the new tabs in any 0.8.x release. They are pretty stable at the moment, but they are a big enough change that we won’t risk releasing them until they’ve been tested quite a bit (and that means 0.9). Any further 0.8.x releases will only include critical fixes. At the moment, we are thinking about releasing version 0.8.2 to fix the fact that we have buggy Firefox bookmark importing. In fact, Camino 0.8.1 won’t even offer to import bookmarks from more recent builds of Firefox since the Firefox developers have yet again changed the location of their bookmark file. Furthermore, a bug in our Firefox bookmark file parsing sometimes causes folder hierarchies to get messed up. Both of these bugs have already been fixed in nightly builds.
We are putting most of our effort into moving forward with 0.9, a release that can and will include lots of cool new features. New tabs are in our nightly builds already. Geoff, the tabs developer, is working on making them even better. We plan to overhaul our keychain support, which is currently stuck in the past because we had to support Mac OS X 10.1.5 with the 0.8.x releases. Other planned features and fixes include a better organized and feature-complete preference system, all the rendering engine goodness that has happened since Mozilla 1.7, some more privacy tools including browser reset, and the usual slue of bug fixes and optimizations. Oh yeah – lest I forget, we should be replacing parts of our Quickdraw drawing code with Quartz code. I’m not sure when we’ll be drawing entirely with Quartz, but hopefully some time in the next year. Moving to Quartz should give us some speed gains, fewer bugs, and better maintainability.
Anything else you want to know about our plans? Any suggestions? Put well-thought-out questions and comments in the comments for this post and I’ll respond to the good ones as soon as I can.