Several Apache projects (e.g. ServiceMix, Karaf, Camel) moved from Subversion to Git. Is it time for Sling to move also?see discussion on dev@ and SLING-3987
dev@discussions:
- [jira] [Created] (SLING-3987) move from Subversion to Git
- moving sling to git
- [git] Which git system do we want to use?
- [git] Please test sample migrated git projects and repo setup
- [git] Whiteboard migration
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Tools and scripts
Some WIP tools can be found at https://svn.apache.org/repos/asf/sling/trunk/tooling/scm/scripts/ .
Can Sling (committers and contributors) benefit from moving to Git?
...
- offline support
- cherry picking
- easy to move projects (e.g. between bundles, contrib, whiteboard...)
- adpoting the Github workflow using the Git Dual Master system
- ...
Cons
- not eating our own dog food
- slow for big repositories (many modules)
- tagging is global
- ...
...
Repository Layout and Projects (Modules)
There are currently over 280 250 projects (modules) in our repository and only few are reactor/builder (sling, *reactor, *builder) projects:
...
, counted using the tooling/scm/scripts/gen-repo-candidates.sh script.
Idea
- one Git repository per project/module (we should keep it that simple - is launchpad really different, a release unit, Justin Edelson?)
- grouping repositories with Google repo, e.g.
core(bundles),launchpad,testing,samples,toolingas needed - using
artifactIdas repository name for artifacts (bundles, plugins, jars, ...) and simple names for grouping (builder/reactor) repositories - using Google repo allows developers to set up their own grouping repositories - even non Sling committers
...