Re: [cross-project-issues-dev] Fw: [platform-releng-dev] request for M5 rebuild
For my part, I always try to grab the latest stable (minimal JUnit failures) platform I or M as
soon as it's available and spin a nightly build to sanity-check PDE. I usually do this Mon or Wed every week, but in some cases I've been forced to go 2 or 3 weeks (it's rare, because generally things are pretty stable with the linux-gtk builds).
Because of this, I tend to find build-related problems before other teams, like the startup.jar change. In that specific example, we had a fix in place before a lot of teams even knew there was an impending problem coming their way. Particularly between M4 and M6, this is crucial if you're going to have time to get a fix into an upstream dependency before your next milestone. Sure, it's a bit more work to stay current, but for *my* own sanity, I'd rather know a problem exists early and have time to open bugs & research fixes than to have to scramble to solve a problem at the last minute, miss a deadline, or have to respin a milestone.
Oh, and if you want to ensure you always have the latest Platform or Modeling build so you can always be building/testing with the latest, there's an RSS feed for each, so you can set up your local environment to collect the latest automatically. ;-)
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling