Community
Participate
Working Groups
Migrate the Graphiti sources from CVS to GIT
Probably a must-have for Juno
There's a migration guide at http://wiki.eclipse.org/Git/Migrating_to_Git. - Git concepts need to be clear - Caveats exist but are ok: contributions cannot directly be pulled from contributor's GIT repository and pushed to Eclipse GIT for IP reasons . Handling is described in http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions or http://wiki.eclipse.org/Image:Git-correct.png - Need to detail out how the GIT space for Graphiti shall look like - Existing code shall be imported including the complete history and branches (b0_7_0RC2 and v0_7_0RC1_b can be omitted) - Migration should be done by Webmaster (triggered via Bugzilla); should use cvs2git
Details for the GIT space for Graphiti. I don't see any reasons why we shouldn't stick to our current layout. This would mean one GIT repository (org.eclipse.gmp.graphiti) containing the folders examples, features, plugins, releng and tests with the complete structure below as today.
The migration request I opened via https://bugs.eclipse.org/bugs/show_bug.cgi?id=353007 was processed by webmaster during the night, first impression is that it is ok. Our Git repository is at http://git.eclipse.org/c/gmp/org.eclipse.gmp.graphiti.git/
I just did a quick search for the term 'CVS' in my workspace and found several places e.g. in the docu that reference the sources via cvsview urls. This needs to be adapted.
Let Webmaster enable https write access to enable push to upstream via https
dev build now works using the sources from Git
Described setup fro Git in Wiki: http://wiki.eclipse.org/GMP/Graphiti#Committer_Git_Access
The 0.8-based build is now also adapted to Git
Complete
Bookkeeping: Set target release
Part of Graphiti 0.9.0 (Eclipse Juno)