To all DTP committers,
Now that the Indigo release is done, the DTP project is planning to migrate our source repository from Eclipse CVS to Git. This is in line with the overall direction of Eclipse projects. We also want to take the opportunity to refine the source organization
and clean up obsolete plugins, as part of the migration.
Below are some high lights of the migration plan. Please review and let us know of any concerns by end of this week. If there are no show-stoppers, we are looking at proceeding with the migration in another week or so. Detail time line will be determined
and sent out after this review period.
1. We are essentially migrating the DTP CVS Head branch to Git, and it will include the history in CVS. If there is ever a need to build DTP 1.9 or older version, it should still grab the source from corresponding CVS branches.
New builds (DTP 1.9.1 and on) will be built from Git. (We are not currently doing any nightly build for 1.9.1 [the Indigo SR1 release]. It will resume when the Git migration is completed.)
2. Separate Git repositories will be created for DTP sub-projects. The main guideline used for the repo separation is to group those highly-related projects that are likely maintained by the same set of committers.
Below are the summary list of separate DTP Git repos. See the attached spreadsheet for the proposed directory structure and content in each repo. Note that obsolete or archived plugin projects will not be migrated, and are thus not included in
the Git repos.
Separate Git source repos for sub-projects and enablement:
where <vendor> are: hsqldb, ibm, ingres, msft, mysql, oda, oracle, postgresql, sap, sqlite, sybase
- org.eclipse.datatools.enablement.general.git (contains non-vendor specific enablement plugin projects:)
Each of the above source repos contain the following sub-folders, if content exists:
plugins/ : contains source plugin projects
releng/ : contains map file of the source plugin projects
tests/ : contains unit test plugins
examples/ : exemplary implementation projects
Additional separate Git repos for non-source projects:
Separately, for those interested in EGit/Git documentation, here are some links:
If you would like to get familiarized with using Git, we have a few temporary test Git repositories on github.com.
Note that the directory structures found in these test repos are not the proposed ones. See the attached spreadsheet instead for the proposed directory structures.
* DTP connectivity project:
URI: git://github.com/YongJiang/DTP_connectivity.git (read only)
* DTP modelbase project:
URI: git://github.com/YongJiang/DTP_modelbase.git (read only)
* DTP sqltools project:
URI: git://github.com/YongJiang/DTP_sqltools.git (read only)
URI: git://github.com/YongJiang/DTP_enablement_ibm.git (read only)
URI: git://github.com/YongJiang/DTP_enablement_oda.git (read only)
To write (e.g. push) to the DTP test remote repos on github, it will need a password: Actuate2011
To browse the content of a remote Git repo, use a web browser with the remote repo URL, e.g.
Linda and DTP PMC