On 4/18/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > And I think that is great when it is something more revolutionary... but > you would agree that you don't take a patch and start a project on SF > and wait for a community to build around it before applying it, right? > If you accept my original thesis that what I was doing amounted to not > much more than a slightly more complex patch, or at most a somewhat > minor upgrade, then the same argument should hold, should it not?
Many mature projects in "evolutionary" mode do pass around patches, and discuss them in detail, before applying them to the HEAD. What you are proposing is not much different than what people did with the Nesting taglibs, or the EL taglibs, or the Faces taglib. In all of these cases, the work was done outside of the head, a community of users developed around the codebase, and then it was made part of the main project. Another good example is Struts Chain. We had Struts Chain in the sandbox for nearly a year before merging it with the HEAD. Things that seem like a minor patch often snowball when integrated into the HEAD. Modules are a good example. Even after we shipped modules in 1.1, we spent months making additional fixes and integrations for 1.2. (Mostly based on user feedback from the 1.1 distribution.) I'd like to see this happen. But, it will be more work than any of us can imagine right now. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
