I didn't want to cause more confusion... what I meant to say is: There were some new builds and contribution from the Eclipse Platform team, but there's no need for us to re-build our builds from yesterday evening.
All RAP builds (1.5.2RC3, 2.0RC3) are fine and already contributed and need some testing. If there's a need for a 2.0 respin in order to pick up some (documentation) changes that's an independent thing and we can do this later today. I hope that clarifies it a bit... Thanks, Markus On Wed, Feb 6, 2013 at 9:39 AM, Ralf Sternberg <[email protected] > wrote: > Hi Markus, > > that's good news, thanks. > > This means that we don't have to test the SR2 RC3 builds you created > yesterday as they won't be contributed, right? > > Regards, Ralf > > > On Wed, Feb 6, 2013 at 9:01 AM, Markus Knauer <[email protected]> > wrote: > > For your information... > > > > The Eclipse Platform team is in their usual M5a phase ;-) and they are > going > > to contribute an updated M5a build to Kepler. I compared the new M5a > > contribution build I20130204-1400 (S-4.3M5a-201302041400) with their old > M5 > > contribution and found no changes in the bundles that we are using in > RAP. > > From that point of view there's no need to rebuild RAP 2.0RC3. > > > > The same applies to Juno SR2 RC3. If the Platform team decides to > contribute > > build M20130204-1200 to the Juno SR2 repository, we are safe and don't > need > > to rebuild our Juno SR2 contribution. > > > > Regards, > > Markus > > > > _______________________________________________ > > rap-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/rap-dev > > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev >
_______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
