----- Original Message ----
> From: "Mattmann, Chris A (388J)" <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: Wed, December 1, 2010 1:42:47 PM
> Subject: Re: Basing Apache releases on releases from incubating projects
>
> Hey Joe,
>
> I agree with pretty much everything you said below. One good thing
> (and correct me if I'm wrong) but is that I interpret what you are saying
>here:
>
> > This is not an academic question. Ask Dims how things worked for
> > Geronimo when they had such a dependency. Basically the expectation
> > is that the dependent project will check the code into their own tree
> > and finish whatever vetting needs to take place. It then becomes a part
> > of *their* release process, not treated as an external dependency (how
> > they bundle that software doesn't really matter).
>
> to mean that it's the decision of the project who is including
> the dependency's source code in their own source code (and that
> is a mechanism to achieve what I'm proposing). If that's what
> you are saying then I agree. Even if that's not, I think I more
> or less am fine with what you're saying and sorry for causing
> everyone the email spam!
>
> I'm putting my head back down to work for the rest of the day! :)
There is a practical difference here between what Geronimo did in their
situation and what say Cassandra did with Thrift pre-release. Cassandra
didn't work to do any vetting of the Thrift codebase, they just packaged
up a jar rolled from trunk and put it up for inclusion in their release
as an external dependency. The IPMC approved those releases without ever
ascertaining whether the Thrift codebase in the Cassandra release had
been vetted- and I know for a fact that it wasn't completely right.
That's not a practice I'd like to see condoned going forward.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
