> 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.
If anyone has questions about CBI, the cbi-dev list is a good place to ask them. Sorry I don't know the direct answer about documentation ... but, I bet there is one ... and those that monitor the cbi-dev list could tell you. Thanks, From: Anthony Hunter <antho...@ca.ibm.com> To: "Cross project issues" <cross-project-issues-dev@eclipse.org>, Date: 08/16/2012 10:42 AM Subject: [cross-project-issues-dev] EMF Validation has not been enabled for Kepler Sent by: cross-project-issues-dev-boun...@eclipse.org 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 cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
