FYI. ECF might leave the simultaneous release train. Reasons why this is potentially bad for us are outlined below. https://dev.eclipse.org/mhonarc/lists/ecf-dev/msg07938.html ---------- Forwarded message ---------- From: Sam Davis <sam.davis(a)tasktop.com&gt; Date: Tue, Aug 16, 2016 at 3:00 PM Subject: [eclipse.org-planning-council] ECF possibly leaving the train To: Eclipse Planning Council private list <eclipse.org-planning-council(a)eclipse.org&gt; Hi, I want to bring to the Council's attention the fact that ECF is considering pulling out of the simultaneous release train, because I haven't seen any discussion about this. This is concerning for a couple of reasons: * a number of projects in the train, including Platform, depend on ECF, so we may end up with different projects pulling in different versions of ECF, which is not ideal * The fact that participation in the train entails so much overhead that an active project with a long history of successful participation is considering pulling out seems like a larger and quite serious problem for Eclipse. I believe at least part of the overhead is due to the instability of the build infrastructure. I'm afraid I don't have any concrete solutions to propose, but I wonder if, given the current resources, we should consider simplifying the contribution process (somehow), or reallocating resources from elsewhere to improve the stability of the infrastructure. Regarding the infrastructure, my experience from the Mylyn project is that projects must spend a great deal of time dealing with broken Hudson slaves, breakages in the signing service, and similar issues, to the point where I can see why it threatens projects' ability to participate. Just to be clear, I am not blaming anyone for this - I know that it takes a lot of work to keep all these things running smoothly. Cheers, Sam -- Sam Davis Software Engineer, Tasktop Dev Committer, Eclipse Mylyn http://tasktop.com _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council(a)eclipse.org https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-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(a)eclipse.org to request removal. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com