I think that leaving the contributions "enabled" would be better than forcing everyone into this situation : we have to load the aggregator, enable our contribution, check if it works... and come back at regular intervals to check for our dependencies' enablement. This is time consuming for those of us who depend on a few projects... and frustrating since we know that we are in turn blocking others. Not to mention that this always comes at a time where most of us are in holidays and just cannot react.
I think this had already been discussed last year, and I do not know if leaving all projects "enabled" by default is better, at least it would not block anything.
Grégoire, Acceleo will be enabled some time tomorrow (CEST), sorry for the wait.
Laurent Goubet Obeo On 22/08/2013 18:11, Grégoire Dupé wrote:
Hello I'm still waiting for Acceleo and ATL (may be more) to deliver MoDisco. It's quite late in Europe; I've to leave the office. I assume that MoDisco will not be included in Luna M1 :-( Regards, Grégoire ----- Original Message ----- From: "David M Williams" <[email protected]> To: [email protected] Sent: Jeudi 22 Août 2013 10:13:05 Subject: [cross-project-issues-dev] Status and Outlook for Luna M1 Ok, it's Thursday morning :) Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done). That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on, but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet. Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc. So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help. Thanks, = = = = = = = = = actf.b3aggrcon - org.eclipse.simrel.build amalgam.b3aggrcon - org.eclipse.simrel.build amp.b3aggrcon - org.eclipse.simrel.build dltk.b3aggrcon - org.eclipse.simrel.build ecf.b3aggrcon - org.eclipse.simrel.build emf-compare.b3aggrcon - org.eclipse.simrel.build emft-ecoretools.b3aggrcon - org.eclipse.simrel.build emft-eef.b3aggrcon - org.eclipse.simrel.build emft-egf.b3aggrcon - org.eclipse.simrel.build gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build gmp-graphiti.b3aggrcon - org.eclipse.simrel.build jwt.b3aggrcon - org.eclipse.simrel.build koneki.b3aggrcon - org.eclipse.simrel.build m2m-atl.b3aggrcon - org.eclipse.simrel.build m2t-acceleo.b3aggrcon - org.eclipse.simrel.build mdt-modisco.b3aggrcon - org.eclipse.simrel.build mft.b3aggrcon - org.eclipse.simrel.build mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build pdt.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build soa-sca.b3aggrcon - org.eclipse.simrel.build windowbuilder.b3aggrcon - org.eclipse.simrel.build _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<attachment: laurent_goubet.vcf>>
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
