On Fri, May 30, 2008 at 2:53 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > 1. Incubator releases go into Central > > 2. Regular releases cannot use Incubator artifacts > > > > Since the whole point of the incubator releases is to get some people to > use them and prove them out, I say 2 is not really an option. If the PMC > of a given project tests out an incubator artifact and deems it good > enough for a release, then that should be enough.... But let's make it > easier for the users by having those dependencies available. > Imho, #2 is not a good option. Projects are allowed to use external dependencies if their license is compatible. This is a legal issue. Incubator releases are obviously under the ASL, so as Dan said, the only thing is that it would make building a community harder for the podling, without any real benefits imho. In particular, this is really weird for projects coming into the incubator with an existing code base and a community. ASF projects would be able to use the pre-incubator versions, but not the releases published while inside the incubator ? I really thing it's up to the PMC to decide if they want to depend on some incubating projects or not and I'd say we should even encourage that to help building the community around the incubating project. -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
