THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This page will contains various Apache Maven svn and their ETA of Git Scm migration: 
Waiting for volunteer, 
Work in progress, 
done, 
to be discussed, 
do NOT do 
aggregator strategy to define
Project | ETA | Details/comment | Volunteer for migration | Infra Jira | ||
|---|---|---|---|---|---|---|
/ant-tasks |
|
deprecated |
app-engine | /app-engine |
|
never released... |
/archetype |
|
/archetypes |
|
Hervé Boutemy historically, all archetypes were released in 1 release, but since a few years, every archetype is released independantly |
require a svn2git mirror first: |
components | /components |
|
/core-integration-testing |
|
/doxia/doxia |
|
/doxia/doxia-ide |
|
maven-doxia-ide.git | really alive? |
let's start with a svn2git mirror: |
/doxia/doxia-sitetools |
|
/doxia/doxia-tools |
| maven-doxia-converter.git | ||||
/doxia/site |
|
same as Maven site: Hervé Boutemy AFAIK, infra only supports svn for CMS |
require Jenkins credentials to publish to svnpubsub: |
/enforcer |
|
/indexer |
|
/jxr |
|
Maven 1 | /maven-1 |
|
Maven 2 | /maven-2 |
|
Olivier Lamy migrate this really ? |
Maven 3 | /maven-3 |
|
/plugin-testing |
| current git@asf repo is ok | ||||
/plugin-tools |
|
/plugins |
|
|
Kristian Rosenvold: Existing git repo @ apache can NOT be used
/pom |
Olivier Lamy migrate this really ?
Hervé Boutemy: ASF parent and Maven parent don't have same release schedule, then would be split in 2 git repos
| see migrate-pom.sh | |||
Project | /project |
|
Olivier Lamy no migration |
/release |
|
svn2git RO mirror to github = https://github.com/apache/maven-release/
repository-tools | /repository-tools |
|
maven-repository-tools.git | |||
/resources |
|
Olivier Lamy: need to be discussed more |
retired | /retired |
|
Olivier Lamy: no migration |
Sandbox | /sandbox |
|
maven-sandbox.git | Olivier Lamy: migrate this really ? |
Hervé Boutemy created maven-studies.git to have an equivalent on Git | |||
scm | /scm |
|
/shared |
|
|
Kristian Rosenvold: thinks this repo should be split into separate projects |
/site |
| maven-site.git |
Hervé Boutemy AFAIK, infra only supports svn for CMS |
=> will disable CMS require Jenkins credentials to publish to svnpubsub: |
/skins |
Olivier Lamy: need to be discussed more
| see migrate-skins.sh | |||
/surefire |
|
/wagon |
|
Migrating an aggregator tree into a collection of git repos
...
No strategy currently found on these 3 topics. Apache Sling seems to have the same work in progress (10/2017): see SLING-3987 and corresponding Wiki page for planning (equivalent to this one for Maven).
Update 11/2017: strategies found for every issue (ignoring Sonar for now):
- git repos split scripts created (inspired from Sling),
- Google repo manifest created in https://github.com/hboutemy/maven-aggregator (inspired from Sling),
- Jenkins "ASF Organization" plugin WIP: see sconnolly videos that lead to maven-box and maven-wip Jenkins jobs
| aggregator | content | Jenkins | Sonar |
|---|---|---|---|
| plugins |
| : ASF and maven | 2 jobs: maven-parent ASF Parent Pom | N/A |
| resources |
| 6 resources | 1 aggregator job: maven-project-resources | N/A |
| shared |
| 26 shared components | 2 aggregator jobs: maven-shared maven-shared-windows | Maven Shared Components Aggregator |
| skins |
| 2 skins (3 obsolete) | 1 aggregator job: maven-skins | N/A |
| doxia-tools |
| 4 tools | 1 aggregator job: doxia-tools | Doxia Aggregator |
| archetypes |
TODO: delete svn2git mirrors once split: maven-pom.git, maven-skins.git
Keeping track of authoritative SCM for each plugin
...
Update the Source Repository page (see also Doxia Source Repository).
For projects providing a plugin, we also keep track of which SCM by modifying the Available Plugins 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)
...
use Apache review board ? https://reviews.apache.org ?