There's been a lot of gnashing of teeth and swirl in the builds lately. Both are probably, at some level, connected. Mozilla changes have been adversely affecting camino, we're finding bugs in panther that affect camino, and we're still trying to get the huge bookmarks rewrite straightened out as quickly as possible. Swirl.
I think we all agree that we need to hit 0.8 to give people something to use that's not 0.7 and doesn't have the instability of the nightlies. Depending on the timing, moving to the 1.6 or 1.7 branch would allow us to focus more on camino and less on mozilla, just like when we were on the mozilla1.0 branch driving to 0.7. I think a lot of people were spoiled in that timeframe as we were never surprised by regressions from outside.
However, we have a lot of work to do to get back to the polish level of 0.7. As I've said before, we are victims of our own success. There are also many things that I don't think will make 0.8 if we hope to get it out in any reasonable timeframe, Java being a big one. Nobody has time to rewrite our entire java impl for 1.4 and apple no longer supports 1.3. That might just have to wait. As with other things, if that's unacceptable to you, patches are always welcome. A trite answer, but true.
I will be taking my sabbatical (6 weeks) starting in january, and I'll have more time to work on camino then. I think that would be a good time to focus our drive to an 0.8 release. In the meantime, we have to decide on what is most important for 0.8. I'm trying to think of the best way to do that. I also doubt we'll be able to drive anything effectively during the holidays (just a hunch).
Let's take the last few weeks (in builds and on the mailing list) with a shaker of salt, and focus on the product we're here to build.
-- Mike Pinkerton Mac Weenie [EMAIL PROTECTED]
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
