Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Impossible to find subset of "aggregated" CQs to piggy-back

It is not intended that anybody piggyback this style of aggregate CQ. In fact, it should be marked as "nopiggyback".

This is a relatively new exception/workaround that we still need to document.

The short version is this:
  • One CQ may contain many or all of the dependencies
  • Node.js dependencies only
  • The CQ must be "Type A"
  • Attach the sources for all dependencies as a single ZIP file
  • The CQ is tied to a specific project; no piggybacks.
HTH,

Wayne

On Fri, Oct 12, 2018 at 6:33 AM Mickael Istria <mistria@xxxxxxxxxx> wrote:
Hi,
What's the best process to make sure this get considered at some point? Should I open a bug now or do we need further discussion from the AC?
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25


Back to the top