Sources Git migration ETA
This page will contains various Apache Maven svn (see trunks (/https://svn.apache.org/viewvc/maven/trunks/)) and their ETA of Git Scm (see git repositories) migration
Project |
Svn Path |
ETA |
Git Repo URL |
Details/comment |
Volunteer for migration |
Infra Jira |
---|---|---|---|---|---|---|
ant-tasks |
/ant-tasks |
|
|
|
|
|
app-engine |
/app-engine |
|
|
|
|
|
archetype |
/archetype |
|
|
|
bimargulies |
|
archetypes |
/archetypes |
|
|
|
|
|
components |
/components |
|
|
Olivier Lamy: migration for this ? |
|
|
core-integration-testing |
/core-integration-testing |
|
Olivier Lamy: makes sense to migrate when migrate maven-3 core |
|||
doxia |
/doxia |
|
|
Olivier Lamy: contains some sub projects (having one git repo per sub doxia module ? |
|
|
enforcer |
/enforcer |
|
|
|
|
|
indexer |
/indexer |
|
|
|
||
jxr |
/jxr |
|
|
|
|
|
Maven 1 |
/maven-1 |
|
|
Olivier Lamy migrate this really ? |
|
|
Maven 2 |
/maven-2 |
|
|
Olivier Lamy migrate this really ? |
|
|
Maven 3 |
/maven-3 |
|
krosenvold: existing git repo@apache can be used as-is |
|||
Plugin Testing |
/plugin-testing |
|
current git@asf repo is ok |
krosenvold |
||
Plugin Tools |
/plugin-tools |
|
|
|
|
|
Plugins |
/plugins |
|
|
Olivier Lamy: ouch ! need to be discussed more. krosenvold: Existing git repo @ apache can NOT be used |
|
|
Parent Poms |
/pom |
|
|
Olivier Lamy migrate this really ? |
|
|
Project |
/project |
|
|
Olivier Lamy no migration |
|
|
Release |
/release |
|
|
Baptiste Mathus has verified existing git clone to be ready for migration |
krosenvold |
|
repository-tools |
/repository-tools |
|
|
|
|
|
resources |
/resources |
|
|
Olivier Lamy: need to be discussed more |
|
|
retired |
/retired |
|
|
Olivier Lamy: no migration |
|
|
shared |
/shared |
|
|
Kristian Rosenvold: thinks this repo should be split into separate projects |
krosenvold |
|
sandbox |
/sandbox |
|
|
Olivier Lamy: migrate this really ? |
|
|
scm |
/scm |
|
|
|||
skins |
/skins |
|
|
Olivier Lamy: need to be discussed more |
|
|
surefire |
/surefire |
|
Existing git@apache repo can be used as-is |
krosenvold |
||
wagon |
/wagon |
|
|
Keeping track of authorative SCM for each plugin
As a project is migrated, the last commit in svn for that project should typically change the scm url (or invalidate it).
We keep track of which SCM by modifying the plugin/component overview page, much like we do for the
release process (the pages where we update the version numbers of the latest release also contain SCM url, update this
and republish site when a project is migrated)
Things to discuss with INFRA
Could we have some kind of top-level git url for maven alone ? (At least at the logical level; git://git.maven.apache.org or similar ?)
Who coordinates updates of the github mirrors ?
How do we migrate an individual project.
Migration process description
If there is an existing read-only git mirror, and it is appropriate quality (check especially behaviour on checking out tag)
1. Have infra make the existing read-only mirror the official master.
2. Change scm url in pom
3. Update github mirroring url (file issue with github)
4. Celebrate
Else:
Decide on scope of repository. Make git repository. Infra might help; they're a PITA to run from git-svn remote.
Have community review of repository.
Then as above
Could we have some kind of top-level git url for maven alone ? (At least at the logical level; git://git.maven.apache.org or similar ?)
Who coordinates updates of the github mirrors ?
How do we migrate an individual project.
Setup review board
use Apache review board ? https://reviews.apache.org ?