16 CET is indeed 10 eastern.The EEF build is running a little late, but is in signing process at the time of writing. It will be ready and promoted on time for the aggregation.
A build a 12 eastern means 18 CET, we will remain ready to react if this aggregation fails for any reason that seem related to any of the EMFT/EEF, M2T/Acceleo or EMF/Compare projects.
...The build ended successfully before I finished writing this. It is now available on its update site and its ready to be grabbed by the aggregator.
Laurent Goubet Obeo On 16/02/2012 16:09, David M Williams wrote:
I think this is a reasonable request and will re-enable to aggregation build to pick up the change. (Including M2T/Acceleo and EMF/Compare mentioned in another note). If I am reading timeanddate.com correctly, 16 CET is 10 Eastern, so lets plan on 12 noon (Eastern) to start the respin. That allows a few hours for other requests to come in, where projects might be in different timezones, etc., and I would prefer to do only once more, if at all possible. (And do let me know if I'm mapping CET to Eastern time incorrectly). This respin will also include an update for the WTP-Libra project. In their case, they can't blame it on the infrastructure issues, (simple mis-communication about cutoff dates or mistake in updating b3aggrcon file) but includes some bug fixes that have been "done" for a while, and would be hard to obtain via patches. Their contribution will not effect EPP Packages and not require re-testing by anyone not using Libra directly. Do let us know if anyone one else has good reason to contribute to 12 Noon Eastern respin (that is, please don't just "sneak it in") and what would be impacted, EPP packages, retesting recommended, etc. and, of course, say if you can't quite make 12 noon but need a few more minutes. Assuming we start at 12 Noon, and no build breaks (or, infrastructure problems :/ ) the new ..../releases/maintenance repo will be done about 2 PM Eastern, and the EPP packages rebuilt by roughly 6 PM Eastern. Good thing our plan contains a buffer. :) But this respin will require vigilance for build breaks since it is possible for even unrelated projects to "break" in various ways so to all projects please respond quickly if there are any "failed" messages. Thanks, From: Laurent Goubet<laurent.gou...@obeo.fr> To: Cross project issues<cross-project-issues-dev@eclipse.org>, Date: 02/16/2012 09:25 AM Subject: [cross-project-issues-dev] Requesting a respin for Indigo SR2 Sent by: cross-project-issues-dev-boun...@eclipse.org Hi Folks, There have been quite a number of issues this time for the release... The shell access of our release engineer for EMFT/EEF was blocked on tuesday, then yesterday's outage prevented us from commiting a last-minute fix for a blocking bug, and finally even with the outage resolved, our IP was black listed which resulted in us being unable to either commit or promote any build (this is all CET time). We tried our best to keep you informed of what was going on, Goulwen sent two mails on this list to warn of the EEF project issues Our access to the Eclipse servers was only just restored before noon CET today. We will finally be able to push our fix on the repository and get our final build done. We expect it to be out and promoted at 16 CET. The bugs we should be fixing with this RC are quite severe and impacted business usage of the project by some of its clients. One such example is https://bugs.eclipse.org/bugs/show_bug.cgi?id=371745. We would need a respin of the Indigo SR2 aggregator as well as a respin of the Indigo SR2 modeling package. Are there any objections? Laurent Goubet Obeo[attachment "laurent_goubet.vcf" deleted by David M Williams/Raleigh/IBM] _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<attachment: laurent_goubet.vcf>>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
