Hi Ed, cc Webmaster
Thanks Ed for working on this.
Maybe someone from the foundation can help with that tooling? I
believe the webmaster team is pretty good in writing awesome shell
scripts which could extract that stuff from the MANIFEST.MF files.
This "silly" CQ Piggyback process consumes values resources both on
committer, PMC and foundation site.
Best regards, Lars
On Tue, Aug 18, 2015 at 11:04 AM, Ed Merks <ed.merks@xxxxxxxxx> wrote:
Alexander,
I'm still working with the IP committee on that, in particular on tools to
automatically determine dependencies from p2 update sites or git
repositories so that no CQs are needed to gather the information.
Unfortunately it's volunteer work and I've not had no time for several
months for further effort on that.
Regards,
Ed
On 18/08/2015 10:59 AM, Aleksandar Kurtakov wrote:
Hi everyone,
I remember discussion few months ago for removing the need for piggyback
CQs. What is the status? Do we need to have some formal vote in the
Architecture Council for moving ahead? Or it's pending somewhere else? This
is one of the small things that would ease things both on devel and IP sides
so getting it formalized soon will benefit everyone.
Alexander Kurtakov
Red Hat Eclipse 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.
_______________________________________________
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.