> i agree that many of good quality contributions should also release as > part > of the qooxdoo under different name space , may be qx.contrib inside > official release. > That way those contributions are also making sure that they are compatible > , and reach quality of core qooxdoo .
I don't think we have the resources to support such an approach. A "release train" like this puts enormous demands on both the people releasing the core package as well those providing the contributions, just think about planning, hand-over protocols or synchronization. Eclipse has such a model, and from all I can say it is a very tough regimen. We all wish for high-quality contributions but I think the core team can only provide collateral support for that, but not enforce it. - On the other hand, I don't see anything wrong with a good contribution that catches up with a new release 2 or 3 weeks later. They don't have to be ready all at the same time. T. ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
