This milestone depends on a specific I-build of the Eclipse SDK,
which is available on the server for a limited time only.
However, now that all the infrastructure on foundation servers
is setup to build and test the OTDT, I can easily create a second
more durable milestone 2 once Eclipse 3.6 Milestone 7 is
publicly available (scheduled for May 7).
I'd like to draw your attention to https://bugs.eclipse.org/310434
which speaks about configuration files that need updating after
upgrading to OTDT 0.7.x. If you see problems with manually
updating the affected files (like .project ...) please make yourself
heard at the bug (e.g., by voting). Otherwise I might find more
interesting features to add than writing migration wizards ...
Behind the scenes most efforts as of late went into fixing regressions
that were caused by the big refactoring. After all, moving to Eclipse
actually triggered some significant code cleanup.
I hope this results in even better stability of the tooling.
I should mention one new feature that was initially discussed in
this forum: M1 includes an initial implementation for bugs https://bugs.eclipse.org/304728 + https://bugs.eclipse.org/304729 :
support for serializing teams (second strategy).
Feel free to experiment with this solution and provide feedback
either on the bugs or here in the forum.