| Re: [eclipse.org-architecture-council] Impossible to find subset of "aggregated" CQs to piggy-back |
_______________________________________________Ok for the current state.On Fri, Oct 12, 2018 at 6:43 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:It is not intended that anybody piggyback this style of aggregate CQ.That's too bad.So if one needs a subset of the CQ, instead of doing a piggy-back, this will require a new CQ and duplicate work from committer and IP team?This is a relatively new exception/workaround that we still need to document.Ok. Is the code of https://projects.eclipse.org/projects/tools.wildwebdeveloper/cq/create available somewhere so we could make a PR to document that on the entry point? It seems to be a fairly important and powerful use-case many projects will like to take advantage of from now on.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.
However, I think this could be improved by allowing piggy-back (see my 1st question) to hopefully reduce the workload on committers and IP team.
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.