Sources Git migration ETA

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

Migrating an aggregator tree into a collection of git repos

We have a few agregator trees that have to be split in a collection of git repos.

For each aggregator, there are currently a few Jenkins jobs (corresponding to misc Maven or JDK versions) that will require to be split too. Sonar configuration will require rework too.

And general question: how to clone/update such a collection of git repos (to avoid working on each repo individually)?

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

TODO: delete svn2git mirrors once split: maven-pom.git, maven-skins.git

Keeping track of authoritative 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).

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)

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 (see http://git.apache.org/), and it is appropriate quality (check especially behaviour on checking out tag)

1. Have infra make the existing read-only mirror the official master (see INFRA-5266 for example).
2. Change scm url in pom
3. Add .gitattributes to configure line endings
4. Update github mirroring url (file issue with github) (Hervé Boutemy probably now done by infra on step 1)
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, interpolated SCM info in sub-modules is wrong, and info report displays the 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 2.8 to simplify things (MPIR-290). and to improve explanations for release tag (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 ?