[rt-pmc] [CQ 2561] Apache tomcat Version: 6.0.16

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2561





--- Comment #25 from Barb Cochrane <barb.cochrane@xxxxxxxxxxx>  2008-10-06 13:15:03 ---
Hi Thomas,

Sorry it's taken so long to respond.  No excuses:  just busy busy busy!  :-)  

The autoscan tool was implemented to bring nested jars or zips to the attention
of the committers so they could take immediate action to break them out into
separate CQs.  

We ask for one CQ per jar for a number of reasons, including:
        a)  a jar file is a reasonable level of granularity (not the minimum
level, but a reasonable one) that a project might choose to consume; and
        b)  we need to standardize on a policy because we aren't users of the
applications in question; the bandwidth and consultation required to make a
subjective call on which jars should be included vs. which jars should be
broken out, on a case-by-case basis, would have the effect of slowing down the
actual review work; and
        c)  if nested jars were allowed on each CQ, the CQ summary with the top
level source does not give us an accurate view of the IP that has actually been
reviewed, which could lead to projects not being able to select applications to
piggyback on, duplication of effort and longer wait times for CQ resolution

As for the zip files, their nomenclature leads us to believe they are from
separate sources, hence the requirement for 3 distinct entries.  

It might not be a perfect solution for every scenario, Thomas, but it is the
one that seems to work so far.  

I hope this helps!

Barb


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.