If I have not got it all wrong.. They are making Dolphin with their CMS that is under development also.
I don't know what framework is used though.. Their own php framework?
With framework, I think of a php framework. And a cms is the gui - to make stuff like dolphin pages with a mouse and half a keyboard.
Some php frameworks are emerging from "beta", like Flow3 (with the cms Typo3 optionally used on top).
Anyone know if they make all of these?

If it is the case, that all in the see more same time they are developing - framework, cms, apps/scripts..
I guess they have a lot of code to view for most bugs and changes.

As for release cycle,
I guess released more often - with upgrade scripts - there would be a large increase in support questions also.
(something went whops during my upgrade, what happened to.. etc..)

I'd be happy to see a focus on frequent security patches (many touching the "function A -> function K" includings probably).
(have you checked your logs from 6.1.4 - 6.1.6..? here they still try to include c99 shells 10 times a day on the current D7 - search ".txt?"..)

Also a listing by area. Like chat fixes, privacy fixes etc..
I would then only pick the updates we need, and avoid the rest until "stable".
I am moving to dolphin from a site with about 3000 known bugs.. So I for one was very happy with the release of D7. :D

Also, very good point in the first post, about a team working together on 8 bugs in symphony rather than 100 in a clash.
Many of the bugs listed do not bother me at all, or are simple fixes or feature requests.
Perhaps having one list for the important (voted?) ones - say 8 core bugs - and have main team working closer together on them.
And sending bug reports to a maintainer, that reviews and adds bugs in a fixed way. instead of reclassifying and briefly changing comments etc..

Im anyway optimistic on D7, but ask me again at the end of the year :)


-AA