Re: [linuxtools-dev] Helios IP Reviews due by 5 February

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Just to clarify the purpose of this
process, the CQ's exist mainly as a way of documenting dependencies. Filing
a CQ allows them to be harvested and documented automatically by the IP
log tool, which is far better than trying to do this by hand. The main
thing you need to decide is whether it is a "works with" or "pre-req"
dependency. "Works-with" means it is optional or interchangeable,
wherease "pre-req" means you can't possibly work without it.
Full details are in the 3rd party dependency doc [1]. The works-with dependencies
just need to be documented in a CQ and you are done. The "pre-req"
dependencies need approval of the EMO so the review process is a bit more
involved. In the end, any third party code that your stuff calls or somehow
invokes needs to be documented.

[1] http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf

John

Andrew Overholt <overholt@xxxxxxxxxx>
Sent by: linuxtools-dev-bounces@xxxxxxxxxxx

01/19/2010 10:29 AM

Please respond to
Andrew Overholt <overholt@xxxxxxxxxx>; Please respond to
Linux Tools developer discussions <linuxtools-dev@xxxxxxxxxxx>

To	Francois Chouinard <fchouinard@xxxxxxxxx>
cc	Linux Tools developer discussions <linuxtools-dev@xxxxxxxxxxx>
Subject	Re: [linuxtools-dev] Helios IP Reviews due by 5 February

Hi Francois,

> We don't *distribute* that library, we only provide instructions on
> how to download, compile, install and configure it.
> 
> Do we really need a CQ for that?

Yes, any and all dependencies need CQs, too.

Andrew
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev