Sources Git migration ETA
This page will contains various Apache Maven svn and their ETA of Git Scm migration
Project |
Svn Path |
ETA |
Git Repo URL |
Details/comment |
Volunteer for migration |
|---|---|---|---|---|---|
ant-tasks |
/ant-tasks |
|
|
|
|
app-engine |
/app-engine |
|
|
|
|
app-engine |
/app-engine |
|
|
|
|
archetype |
/archetype |
|
|
|
|
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 ? |
|
Maven3 core |
/maven-3 |
|
|
krosenvold: existing git repo@apache can be used as-is |
|
Plugin Testing |
/plugin-testing |
|
|
|
|
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 |
|
|
|
|
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)
Setup review board
use Apache review board ? https://reviews.apache.org
?