Nicolas De Loof wrote: > Just a question about releasse process : it seems 1.1 has too much > fonctional enhancements to "quickly" get a release, > and I've read here that future versions will get less improvement, so > that it can be release a simplier way. How will > commiters decide future enhancements ?
The issue wasn't so much that there were so many enhancements, but that
we neglected to make point releases along the way. So, by rights, this is really like Struts 1.8. With 20:20 hindsight, there should have been point releases after adding the nested-taglib, after adding module support, after adding the validator, after adding tiles, after adding the JSTL lib, and so forth.
Moving forward, if someone were to start to add another enhancement (or
"product change") while another was already unreleased in the nightly build, I would veto the change and force a point release. (And if I didn't I'm sure someone else around here now would.) The justification being that we simply don't have the resources to support releasing so many changes at once.
The other issue was moving dependencies to other products. We should now make a point release before (or after) moving or adding any dependencies, even if it is to a Commons product. The next thing on my radar is moving some dependencies to Commons Resources. So as soon as we do that and the code seems stable, it should trigger a point-release.
Since we are all volunteers here, what gets done depends on who is willing to actually do something. There is no hierarchy; individual committers decide what they want to work on, and then other developers chip in as they wish. But, we can each veto any product change we believe is technically unsound, which provides a check and balance.
Most of us are working stiffs, so we tend to do things that we need for our own applications. The vast majority of changes to Struts come about from developers submitting patches they made so that their own applications became easier to write.
-Ted.
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
