Jump to: navigation, search

Difference between revisions of "Ganymede/Final Daze/Modeling Project"

m
m
Line 21: Line 21:
 
* To facilitate this ordering, we will use a number of communication methods to announce when builds are done.
 
* To facilitate this ordering, we will use a number of communication methods to announce when builds are done.
 
:* post to #eclipse-modeling on [[IRC]] -- [[IRC#How_Do_I_Choose_An_IRC_Client.3F|problems connecting?]] Try http://www.mibbit.com.
 
:* post to #eclipse-modeling on [[IRC]] -- [[IRC#How_Do_I_Choose_An_IRC_Client.3F|problems connecting?]] Try http://www.mibbit.com.
:* post to modeling-dev@eclipse.org
+
:* post to modeling-pmc@eclipse.org (and/or modeling-dev@eclipse.org, if it's working -- see {{bug|236300}})
 
:* wiki updates to the [[Ganymede/Signoffs|Ganymede Signoffs]] page, changing status codes to {{status|P|blue}}romoted.
 
:* wiki updates to the [[Ganymede/Signoffs|Ganymede Signoffs]] page, changing status codes to {{status|P|blue}}romoted.
  

Revision as of 16:34, 23 June 2008

Addenda for the Modeling Project builds

Freezing ray.jpg
  • *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.
0. Platform
1. EMF+XSD, GEF, Orbit
2. UML2, JET, Teneo, Compare, Mint, Net4j
3. OCL, ATL, CDO
4. Query, Validation, Op QVT
5. Transaction
6. GMF
7. UML2 Tools, Ecore Tools
8. Search
  • To facilitate this ordering, we will use a number of communication methods to announce when builds are done.
  • When the servers unfreeze, the Ganymede Signoffs page should be updated to use Released.