I don't think there is a simple answer, other than the general rules of three +1s and source code required. However, Java code has additional concerns related to classpath conflicts that could make distributing snapshots harmful to the origin project.
My first try would be to jump over to that other project, build a release package containing just the last release plus fixes, and then ask the other project for three +1s. If that failed, I would try to distribute just a released version and add override classes/methods where necessary. Lacking that possibility, I would copy/paste the code and change the class names, essentially creating a temporary fork. I don't think that Incubator podlings should be any different from regular projects in this regard, and I don't think we should prevent them from doing what needs to be done to cut a release. I think it is very healthy for a podling to think about it first, discuss the options with the other Apache project second, and then do what is best for the podling's product based upon those discussions. ....Roy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
