Contrary to what I first announced, let's
stay on the Aggregator Editor version 0.1 (on Eclipse 3.6) instead of moving
up to 0.2. At least for Juno M1. There is either a bug blocking us (bug
or I've made some sort of error in "converting" our files (or,
both). Either way, there is not enough time to sort that out before M1,
so let's move back to the same version of the b3 Aggregator we use for
Indigo ... and let the fun begin! So, _now_ you can expect lots of errors
to show up, as Kim updates the Platform's contribution to 4.2 M1.
Sorry for the churn ... greatest thanks.
David M Williams/Raleigh/IBM@IBMUS
08/10/2011 02:12 PM
Juno aggregation builds are ready, and
Indigo has moved to 'maintenance'
I have setup and started the Juno aggregation builds, using the previously
contributed indigo b3aggrcon files as a starting point. I have promoted
the initial Juno test-build to the staging repo, and confirmed the current
results are nearly identical, as would be expected. http://download.eclipse.org/releases/staging/
There are a few things to point out:
* If anyone was in Indigo, but will no longer be in Juno, please let us
know, so we can remove your project files sooner rather than later.
I will update the google calendar soon. The only change from previous version
was the M6 end date and M7 start date change by 1 week, so they'd each
be a balanced 7 weeks now, and fit in better with EclipseCon.