Thanks Kim, for the early submission and letting us know of this important final submission. (And, I even re-enabled the PDE/EE feature for you :)
But, ... point of this note, to be clear to all ... I have disabled Indigo aggregation builds for today ... to wait until RC3 is "out the door" (not to mention give Hudson a rest :) ... and will re-enable them Friday morning. >From my "local build" though it looks like everything will build fine ... even that pesky Riena which normally has to react to each platform change (and, I say "pesky" with the greatest respect ... and quirkiest of humor :) Thanks all, From: Kim Moir <[email protected]> To: Cross project issues <[email protected]>, Date: 02/09/2012 08:12 AM Subject: Re: [cross-project-issues-dev] Declaring Indigo SR2 RC3 staging repo done Sent by: [email protected] I've just contributed 3.7.2RC4 to the Indigo build. Kim From: David M Williams <[email protected]> To: [email protected] Date: 02/08/2012 07:27 PM Subject: [cross-project-issues-dev] Declaring Indigo SR2 RC3 staging repo done Sent by: [email protected] Despite Hudson's attempts to thwart our progress, our RC3 repo is done and testable at http://download.eclipse.org/releases/maintenance/ and this one is a true release candidate! (though, I know a few more bug fixes are planned for RC4, our final build). Thanks to all those fixing "legal file" type problems, etc. to get as close as possible to final form. http://build.eclipse.org/indigo/simrel/index.html Remember that once we release Indigo SR2, it will joining the Indigo Release and Indigo SR1 repositories as a composite repo, at http://download.eclipse.org/releases/indigo/ This RC3 build will be a good one to test as a "pseudo composite" by careful construction of your software repository list. See http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F This is important to test for things like "updates" (You will have to wait till Friday, to test "updates" if you start with an EPP Package). and to confirm no features/bundles accidentally went "down" in version number or in general other issues that can work fine in isolation, but fail in composite repositories. Test early, test often. Thanks, _______________________________________________ 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 _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
