Sources Git migration ETA
This page will contains various Apache Maven svn and their ETA of Git Scm migration
Project | ETA | Details/comment | Volunteer for migration | Infra Jira | ||
|---|---|---|---|---|---|---|
ant-tasks | /ant-tasks |
|
|
|
|
|
app-engine | /app-engine |
|
|
|
|
|
archetype | /archetype |
|
|
| bimargulies | INFRA-9100 |
archetypes | /archetypes |
|
|
| bimargulies | INFRA-9101 |
components | /components |
|
| Olivier Lamy: migration for this ? |
|
|
core-integration-testing | /core-integration-testing |
|
| |||
Doxia core | /doxia/doxia |
|
|
|
|
|
Doxia IDE | /doxia/doxia-ide |
|
|
|
|
|
Doxia Site Tools | /doxia/doxia-sitetools |
|
|
|
|
|
Doxia Tools | /doxia/doxia-tools |
|
|
|
|
|
Doxia Site | /doxia/site |
|
|
|
|
|
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 |
|
| |||
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. |
| |
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 |
|
|
sandbox | /sandbox |
|
| Olivier Lamy: migrate this really ? |
|
|
scm | /scm |
|
| |||
shared | /shared |
|
| Kristian Rosenvold: thinks this repo should be split into separate projects | krosenvold |
|
Maven Site | /site |
|
|
|
|
|
skins | /skins |
|
| Olivier Lamy: need to be discussed more |
|
|
surefire | /surefire |
|
| 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. Add .gitattributes to configure line endings
4. Update github mirroring url (file issue with github)
5. 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.
Project's SCM info report
When a project has multiple modules, SCM info report gives wrong info: for example http://maven.apache.org/ref/3.1.0/maven-artifact/source-repository.html
Some tweaks in parent pom can be done to improve things: http://maven.apache.org/ref/3.1.1/maven-artifact/source-repository.html
There are improvements to MPIR to simplify things (MPIR-290) and to improve explanations (MPIR-291).
With actual Git Webview configuration at Apache, the only way to have web view is to link to GitHub: need to be improved
Setup review board
use Apache review board ? https://reviews.apache.org ?