Thanks, this saves me from doing some extra work in an already loaded week... :-)
Michael Von meinem iPad gesendet Am 16.08.2012 um 20:09 schrieb "Anthony Hunter" <[email protected]<mailto:[email protected]>>: This makes sense David. I will enable the final Juno bits for Kepler M1 for now. Cheers... Anthony From: David M Williams <[email protected]<mailto:[email protected]>> To: Cross project issues <[email protected]<mailto:[email protected]>>, Date: 2012/08/16 12:47 PM Subject: Re: [cross-project-issues-dev] EMF Validation has not been enabled for Kepler Sent by: [email protected]<mailto:[email protected]> ________________________________ I agree with Anthony, probably not worth changing features, just to be in M1, and think I'll say there will be a blanket exception to anyone who can not participate due to the lack of these prereqs. It'd be unfortunate though, since very few EPP packages could be built without many of these fundamental projects. However, Anthony, I just realized an alternative way to view things. If things do "fall apart in a few months and then have to remove projects from Kepler again" then I'm sure all (or most) current consumers would simply use your previous, Juno release even if you decided these projects would not participate in Kepler. So, is there really any harm in enabling now? That way people could continue to use your Juno release as a prereq in an easy way, and if it turns out you can not build or support these projects in Kepler, you could withdraw at a later time (say before M4), and at that point, consumers would have to change their features/repos to consume the Juno release of these features, similar to how they'd consume an Orbit third party dependency. I think that way we could have your cake and eat it too :) That is, you have given "warning" that there's risk for these projects, but for now (for a milestone or two?) consumers could still use the Juno release and not hold up their own work. Make sense? From: Anthony Hunter <[email protected]<mailto:[email protected]>> To: Cross project issues <[email protected]<mailto:[email protected]>>, Date: 08/16/2012 12:25 PM Subject: Re: [cross-project-issues-dev] EMF Validation has not been enabled for Kepler Sent by: [email protected]<mailto:[email protected]> ________________________________ Hi again, To be clear, the original email threads were about Kepler M1 and this email was intended as a definite not enable for Kepler M1. Lets see where we are at for M2 before we start changing features. Cheers... Anthony From: "Wenz, Michael" <[email protected]<mailto:[email protected]>> To: Cross project issues <[email protected]<mailto:[email protected]>>, Cc: Cross project issues <[email protected]<mailto:[email protected]>> Date: 2012/08/16 11:53 AM Subject: Re: [cross-project-issues-dev] EMF Validation has not been enabled for Kepler Sent by: [email protected]<mailto:[email protected]> ________________________________ Hi Anthony, That comes rather surprising to me. It will force Graphiti and presumably a bunch of other projects to include their usages from EMF Transaction/ Validation and GMF into their own features. Not really lucky about that... I will disable the Graphiti contribution to Kepler again since I will not be able to do that change before monday and do not want to block the aggregation. Michael Am 16.08.2012 um 16:41 schrieb "Anthony Hunter" <[email protected]<mailto:[email protected]>>: Hi Team, I received a bunch of emails about several projects I own on the simultaneous release train, none of which are enabled for Kepler. EMF Validation is the lowest dependency that seems to affect the most projects, GMF Notation, GMF Runtime and EMF Transaction are also on the list. These projects need to move to a new build and Git. Moving to a new build means moving to the CBI / long term support build. The CBI is making good progress but nothing is really documented yet. I have made the decision that I am not enabling these projects for Kepler until the Git migration and the new build is complete. I do not want to enable now, have things fall apart in a few months and then have to remove projects from Kepler again. Sorry for the inconvenience. Cheers... Anthony _______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[email protected]> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[email protected]> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[email protected]> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[email protected]> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[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
