On Sun, 2006-03-26 at 18:26 -0500, Lawrence Mandel wrote: > This may just be because I'm used to a lot more structure working at > Eclipse but I'm a little concerned with the lack of management of the WS > commons projects. (I haven't voted -1 because I know I don't have the > time to back up my request by filling this role.) The previous release of > XmlSchema was only a month ago. Instead of releasing new versions when we > feel like it I'd like to see a set release schedule or at least a set of > new features that will be in the release. How about creating a milestone > plan and declaring the current state and milestone 1 for the next release?
Sorry Lawrence it doesn't work like that in Apache. We don't set a plan and have someone cracking the whip to execute the plan. Developers who care about a codebase and want to improve it work on it because it scratches an itch. Dan pushed 1.0 thru because he wanted it for XFire. Ajith is pushing 1.1 as there are some fixes that Axis2 would like to depend on. There is also the mantra of release early, release often. We don't always keep to it but general wisdom is that its healthy for a project to release early & often. > As a start, can you detail the several crucial bugs that were fixed and > why a release of XmlSchema is required at this point rather than just > continuing on with daily snapshots? Is another project relying on this > release? What benefit is there to declaring 1.1 at this point? Main benefit is that Axis2 could depend on an improved version. You certainly have a right to ask to see what bugs have been fixed .. I assume you've already checked SVN and/or JIRA of course. I can imagine this kind development model is frustrating for you .. but that's the reality in ASF style development. You may want to check out a recent thread on the same topic on axis-dev (and synapse-dev). Sanjiva.
