As a user rather than a developer, my comment would be: The James team did exactly what I wanted - cut a16 - now followed by a17 and a18 to incorporate the improvements over 2.1.3.
There has been significant activity on the mailing lists since a16 and I think this has confirmed the product has an interested and supportive user base. I would be comfortable seeing a18 cut as 2.2.0 and then for V2 to be feature-frozen. The team can then turn their attention to V3 with a timeframe of Q1-Q2/05 for delivery of a potentially usable version. I know timeframe can be contentious and don't want to start a flood of "Only announce timeframe once the product is ready" responses. However, I think it helps everyone involved if there is at least a target timeframe. I haven't looked at the V3 map but would suggest consideration of: 1) Moving to a newer container since Phoenix does not appear to have a long-term future other than maintaining stable. 2) Actively dropping those components which have been announced as deprecated - they have to go at some point and doing so in the V2 - V3 transition with advance warning of some 9 - 12 months for users is reasonable I feel. Anyway, thanks to the team for their efforts in delivering an excellent product! Regards, Roy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
