* Builds should be published in dependency order so that the update sites work correctly. This means we should run in this sort of order, waiting for your dependencies to be available before you run your promote.

+

* Our 20 builds should be published in dependency order so that the update sites work correctly. This means we should run in this sort of order, waiting for your dependencies to be available before you run your promote.

−

:1. EMF, GEF

+

:1. EMF+XSD, GEF, Net4j

−

:2. UML2, JET

+

:2. UML2, JET, Ecore Tools, Teneo, Compare, Mint, CDO

−

:3. OCL

+

:3. OCL, ATL

−

:4. Query, Validation

+

:4. Query, Validation, Op QVT

:5. Transaction

:5. Transaction

:6. GMF

:6. GMF

:7. UML2 Tools

:7. UML2 Tools

−

+

:8. Search

* To facilitate this ordering, we can use a number of communication methods to announce when builds are done.

* To facilitate this ordering, we can use a number of communication methods to announce when builds are done.

*DO NOT* publish your final R builds (using the promo.php page or ./promoteToEclipse.sh) until after Denis turns on his freezing ray, and the servers are frozen. Wait for an email to be sent to cross-projects-issues-dev@eclipse.org (if you're not subscribed already, you should be!).

Our 20 builds should be published in dependency order so that the update sites work correctly. This means we should run in this sort of order, waiting for your dependencies to be available before you run your promote.

1. EMF+XSD, GEF, Net4j

2. UML2, JET, Ecore Tools, Teneo, Compare, Mint, CDO

3. OCL, ATL

4. Query, Validation, Op QVT

5. Transaction

6. GMF

7. UML2 Tools

8. Search

To facilitate this ordering, we can use a number of communication methods to announce when builds are done.