On Sat, Jul 29, 2006 at 11:09:03PM -0700, Jeremy Boynes wrote: > Perhaps it would suffice to make it ASF policy that no official > project should have a dependency on a incubating one (or such a > dependency would be scoped as provided so that the user would have to > explicitly include it).
That would be nice, wouldn't it? Unfortunately, that'd break loads and loads of projects over in java-apache land. The ASF is full of snapshot dependencies on itself (even custom-built-specific-SVN-branch-not actually-released dependencies) and the like. In the end, PMCs have the authority to decide on this all by themselves. It'd be great if we'd endorse some good recommendations on this. Of course, the maven 2 book has lots of them, most quite reasonable...Oh, and I'm giving a talk at the next apachecon about the general case ;) All the incubator can do is make it easy for other ASF projects (and the rest of the world) to identify what releases have some sort of "incubation" status and what that means. LSD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
