I just mean that I don't understand why we need a release if the goal is not to make it attractive to new users, but just tag the existing code some of us allready use in production. If the trunk changes, I'll update my patches to support the features I need (I allready did it when the Dav servlet replaced the proxy servlet).
Maybe I simply have to learn "ASF release guidelines", as I never was implied in an apache project release before. That beeing said, I have no objection about releasing a 0.9, if you consider this usefull. Nico. 2007/4/29, Wendy Smoak <[EMAIL PROTECTED]>:
[moved from the branch merge vote thread] On 4/27/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > I also use this codebase for my corporate job and will contribute to > maintain supported features in future releases. I just don't understand why > a "0.9" release would change about the trunk code to be maintained or not. > Do you just mean that having a (pre)release would make the supported > features included in the roadmap ? We still have to re-code them in the > branch-code. I'm not sure I understand what you mean. I'd like to capture the work you and Arnaud have already done, get those patches applied and release it as 0.9-alpha-2. (or possibly -3 depending on whether I get all the i's dotted and t's crossed for release requirements.) I have no plans beyond a single PMC-approved release of this codebase. I personally don't see the point of adding features to it given that the new branch will soon arrive. In addition to wanting it released because I'm using it, we're also on the wrong side of the ASF release guidelines as they currently stand, and need to correct that. -- Wendy
