Jump to: navigation, search

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

m
m
Line 1: Line 1:
Addenda for the Modeling Project builds:
+
===Addenda for the Modeling Project builds===
  
 
[[Image:Freezing_ray.jpg|right]]
 
[[Image:Freezing_ray.jpg|right]]
  
 
* When your final R build is ready (either because you [[Modeling_Project_Releng/Releasing#Renaming_a_Build_.2F_Releasing_Your_GM_Build|renamed your last RC build]] or because you spun an R build) update the [[Ganymede/Signoffs|Ganymede Signoffs]] page using status code {{status|D|orange}}one.
 
* When your final R build is ready (either because you [[Modeling_Project_Releng/Releasing#Renaming_a_Build_.2F_Releasing_Your_GM_Build|renamed your last RC build]] or because you spun an R build) update the [[Ganymede/Signoffs|Ganymede Signoffs]] page using status code {{status|D|orange}}one.
 
  
 
* '''*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!).
 
* '''*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.
 
* 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.
Line 25: Line 23:
 
:* post to modeling-pmc@eclipse.org
 
:* post to modeling-pmc@eclipse.org
 
:* 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.
 
  
 
* When the servers unfreeze, the [[Ganymede/Signoffs|Ganymede Signoffs]] page should be updated to use {{status|R|green}}eleased.
 
* When the servers unfreeze, the [[Ganymede/Signoffs|Ganymede Signoffs]] page should be updated to use {{status|R|green}}eleased.
 +
 +
[[Category:Modeling]] [[Category:Coordinated]] [[Category:Releng]]

Revision as of 16:21, 22 May 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.
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.
  • post to #eclipse-modeling on IRC
  • post to modeling-pmc@eclipse.org
  • wiki updates to the Ganymede Signoffs page, changing status codes to Promoted.
  • When the servers unfreeze, the Ganymede Signoffs page should be updated to use Released.