[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[mdt.dev] FW: [cross-project-issues-dev] Galileo must-do: The Babel Galileo trainhas been set up
|
Team,
See below for details on how to register your component with
Babel.
Cheers,
Kenn
Hussey
Program Manager, Modeling and Design Solutions
Embarcadero Technologies, Inc. | www.embarcadero.com
82
Peter Street, Second Floor |
Toronto, ON M5V
2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office:
416-593-1585 x9296 Mobile:
613-301-9105
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Denis
Roy
Sent: Monday, March 09, 2009 2:56 PM
To: Cross project issues; Babel committers mailing list
Subject: [cross-project-issues-dev] Galileo must-do: The Babel Galileo
trainhas been set up
Greetings,
As Babel participation is a Galileo must-do, your Galileo map
files may now be entered into the Babel server. Simply log into http://babel.eclipse.org/ and use the FOR
COMMITTERS link. The map file URLs you will be entering should be pointing to
the HEAD stream and should be assigned to the version number you will be
releasing in June 2009.
Once your map files are entered, the Babel server will crawl them every night
and pull all the externalized strings, making them available for
translation.
In June, once your code has been tagged as a release in CVS or SVN, we will
update all the map file URLs to point to the Release tag, not HEAD. The
Babel team will do this for you in June if you tell us what the tag is.
For now, don't worry about it -- we'll remind you later.
As an example, the Eclipse project would be defining the map files for Eclipse
3.5 using the "Download" link in ViewVC HEAD:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/core.map?view=co
For more information on defining your map files in Babel, please see the Babel FAQ for
Committers or ask on the Babel
newsgroup.
|
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev