On Aug 23, 2007, at 10:10 AM, Vamsavardhana Reddy wrote:
One other question... Is it necessary that the plugin (if it tends to be different for Tomcat and Jetty or in another context, say Axis2 and CXF) should be made available for all distributions? I guess we are establishing the procedure now and so wanted to cover as many situations as possible.
It might depend what it is. However in general I think its best to provide plugins for each set of prerequisites. For instance I probably won't object if you don't provide a plugin for tomcat and jeff probably won't object if you don't provide a plugin for jetty :-)
i.e. use your judgement on what is practical and good for the community. thanks david jencks
Vamsi On 8/23/07, Kevan Miller < [EMAIL PROTECTED]> wrote: On Aug 22, 2007, at 3:45 PM, David Jencks wrote: > I'm not sure if/when we've faced this in the past but I'd be > comfortable with: > - moving code to plugins > - announcing it on the dev list > - in 3-7 days pushing a snapshot if there are no major objections Sounds ok. I would expect that we'd have had some advanced warning before the code had been moved into plugins... With such advance notice, I'd say 3 day lazy consensus period is quite adequate. This is somewhat akin to adding a new module to Geronimo server and "deploying" the new jar file to a snapshot repository. Major difference is people tend to watch server development a bit more closely... --kevan
