| Re: [eclipse.org-architecture-council] Piggyback CQs status |
We do now.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=475400
Wayne
On 19/08/15 10:53 AM, Lars Vogel wrote:
Hi Wayne and Ed,
do we have a bug to follow this tooling effort?
Best regards, lars
On Tue, Aug 18, 2015 at 9:57 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
It's on our list. While the webmaster team is indeed great at such things, I'm sure that everybody can appreciate that it's important to get this sort of thing right and that it involves a great deal more than knocking out a few scripts.
We fully appreciate that this is something that the EF needs to own and maintain.
Wayne
On 18/08/15 05:30 AM, Lars Vogel wrote:
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.
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
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 Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________ 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
@waynebeaton
The Eclipse Foundation
_______________________________________________
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.