Re: True CSS support Actually, I think the plan is to release bits and pieces of 5.0 between now and the official 5.0 developer releases to allow developers to progressively migrate to 5.0 which would otherwise require major element changes all at once if it was not handled that way. As I recall, we experienced a time lag during the 4.5 development cycle where developers were leary about porting over their projects because they suspected that more changes were coming.
Version 4.6 has portions of 5.0 code (features) that were deemed ready for release by the core team. It is only my guess, but I expect to see more 4.6 releases with more chunks of 5.0 code as time permits. It makes sense to handle it this way for numerous reasons.
Given past history on the 4.5 development cycle, I expect to see early alpha development releases around late October with a stable release early next year. The core team goes through an alpha cycle to expose developers to the new code (it's currently happening now for 4.6 through CVS), followed by a beta cycle where users get involved in the testing. Users were heavily involved in the 4.5 beta cycle and many last minute changes were added to the core because of their participation. |