Difference between revisions of "Galileo/Final Daze/Modeling Project"
|Line 12:||Line 12:|
Revision as of 17:20, 21 June 2009
- 1 Projects
- 2 FAQ
- 2.1 What exactly should we do, and when?
- 2.2 When should we do our final builds/renames and promote the bits?
- 2.3 When should we "unhide" our builds, making them visible to the public?
- 2.4 Update sites are created only when promoted, right? Can I generate it locally?
- 2.5 What about .build files, used to control input to the Galileo update site?
Below is the list of projects in Galileo which have components. (GEF, GMF, and TMF-Xtext are also in Galileo but are single-component-projects.)
Please ensure that for projects w/ multiple component, only one component promotes their bits at a time. I suggest that each component lead should sign up below with the time they plan to do their promote below, so that no overlapping occurs. It's probably also wise to use #eclipse-modeling on IRC to support more immediate conversation/coordination.
Note that it's perfectly acceptable for multiple projects to publish concurrently, since they each have separate update sites. The only limitation is on components who share a common site.
EMF Time Of Promote EMF (Core) Query Transaction Validation Teneo 22 June, 9:00 am (Netherlands Time Zone) Net4j CDO EMFT EMF Compare Ecore Tools Mint MWE MDT OCL UML2 UML2 Tools XSD M2M ATL QVTO M2T JET Xpand Acceleo
What exactly should we do, and when?
Last year we met on IRC in #eclipse-modeling to make sure that projects were published in the correct order:
The only real limitation w/ the current system is that people should NOT PROMOTE their final, renamed or rebuilt builds AT THE SAME TIME within the same project, as this will corrupt the p2 metadata generation process, and you'll end up with an unusable update site.
When should we do our final builds/renames and promote the bits?
You can promote them as soon as they're ready; there's a file in CVS which controls the visibility of R builds, for example:
If there's a build ID listed in that file, it will NOT be shown on the downloads page, but will be available for the mirrors to pick it up and replicate it. If you remove the entry in the file, it will mark the build visible on www.eclipse.org.
You can even control this file from the promo.php page you use to promote builds:
When should we "unhide" our builds, making them visible to the public?
Update sites are created only when promoted, right? Can I generate it locally?
If you want to test locally on your build server, you can use
/home/www-data/build/modeling/scripts/buildUpdateSite.sh to create the update site without publishing it to download.eclipse.org. Run the script without options to get detailed usage instructions.
You could also just unpack the Update.zip somewhere in /var/www/html/ and test that, too, but that'll only verify YOUR update, not your component's contribution to a shared update site (eg. Query into EMF, UML2 into MDT).
What about .build files, used to control input to the Galileo update site?
Create them by hand, or create them as part of the publishing/promoting script. Your choice.
You can also generate them using
/home/www-data/build/modeling/scripts/promoteToEclipse.sh and the
-coordsiteonly galileo flag. Run the script without options to get detailed usage instructions re: the other required flags.