On 02/01/2010 05:42 PM, Nick Kew wrote:
No votes yet, but +1 on taking a direction that can lead to release. It would be good to see the trunk-vs-dev issue sorted at the same time, so people like me know where to start from when hacking on the edges of the code or contributing patches.
Yes, me too. The goal (I hope) is to merge dev branch back to trunk as soon as possible.
Feature freeze is more commonly associated with commercial software than with Apache. No problem with using it if people are happy working to it, but if anyone thinks there should be no feature freeze, that's at least a legitimate topic for debate.
The worry is that we'd get untested new features onto an otherwise stable (hopefully) release. But, good to know, and I definitely is not biased either way, but I'm pretty sure we'll need to have some guidelines for making sure a release is cut from a trunk that is stable.
More important IMHO is an API/ABI promise: third-party developers should be assured that a plugin developed for 2.0.0 will work for future 2.0.x, preferably without a need to recompile. If there is no such promise, you need to make it clear.
Definitely, 2.0.x will be ABI compatible. Cheers! -- leif
