Child pages
  • Git Migration
Skip to end of metadata
Go to start of metadata

Sources Git migration ETA

This page will contains various Apache Maven svn and their ETA of Git Scm migration: (plus)Waiting for volunteer, (warning)Work in progress, (thumbs up)done, (question)to be discussed, (minus)do NOT do (grey lightbulb)aggregator strategy to define

Project

Svn Path

ETA

Git Repo URL

Details/comment

Volunteer for migration

Infra Jira

ant-tasks

/ant-tasks

(plus)

 

 

 

 

app-engine

/app-engine

(plus)

 

 

 

 

archetype

/archetype

(thumbs up)

maven-archetype.git

 

Benson Margulies

INFRA-9100

archetypes

/archetypes

(plus)

 

 

Benson Margulies

INFRA-9101

components

/components

(minus)

 

 

 

 

core-integration-testing

/core-integration-testing

(thumbs up)

maven-integration-testing.git

 

Olivier Lamy

INFRA-5390

Doxia core

/doxia/doxia

(plus)

 

 

 

 

Doxia IDE

/doxia/doxia-ide

(question)

 

 

 

 

Doxia Site Tools

/doxia/doxia-sitetools

(plus)

 

 

 

 

Doxia Tools

/doxia/doxia-tools

(question)(grey lightbulb)

 

Hervé Boutemy see (grey lightbulb)aggregator strategy

 

 

Doxia Site

/doxia/site

(question)

 

 

 

 

enforcer

/enforcer

(plus)

 

 

 

 

indexer

/indexer

(thumbs up)

 

 

Olivier Lamy

INFRA-5312

jxr

/jxr

(plus)

 

 

 

 

Maven 1

/maven-1

(minus)

 

 

 

 

Maven 2

/maven-2

(question)

 

Olivier Lamy migrate this really ?

 

 

Maven 3

/maven-3

(thumbs up)

maven.git

 

Olivier Lamy

INFRA-5390

Plugin Testing

/plugin-testing

(thumbs up)

maven-plugin-testing.git

current git@asf repo is ok

Kristian Rosenvold

INFRA-5312

Plugin Tools

/plugin-tools

(plus)

 

 

Olivier Lamy

 

Plugins

/plugins

(question)(grey lightbulb)

 

Olivier Lamy: ouch ! need to be discussed more
Kristian Rosenvold: Existing git repo @ apache can NOT be used

Hervé Boutemy see (grey lightbulb)aggregator strategy

 

INFRA-5276

Parent Poms

/pom

(question)

 

Olivier Lamy migrate this really ?

Hervé Boutemy: ASF parent and Maven parent don't have same release schedule

 

 

Project

/project

(minus)

 

Olivier Lamy no migration

 

 

Release

/release

(plus)

 

Baptiste Mathus has verified existing git clone to be ready for migration

Kristian Rosenvold 

INFRA-5312

repository-tools

/repository-tools

(question)

 

 

 

 

resources

/resources

(question)(grey lightbulb)

 

Olivier Lamy: need to be discussed more

Hervé Boutemy see (grey lightbulb)aggregator strategy 

 

 

retired

/retired

(minus)

 

Olivier Lamy: no migration

 

 

sandbox

/sandbox

(question)

 

Olivier Lamy: migrate this really ?

 

 

scm

/scm

(thumbs up)

maven-scm.git

 

Olivier Lamy

INFRA-5266

shared

/shared

(question)(grey lightbulb)

 

Kristian Rosenvold: thinks this repo should be split into separate projects

Hervé Boutemy see (grey lightbulb)aggregator strategy 

Kristian Rosenvold 

 

Maven Site

/site

(question)

 

Hervé Boutemy AFAIK, infra only supports svn for CMS

 

 

skins

/skins

(question)(grey lightbulb)

 

Olivier Lamy: need to be discussed more

Hervé Boutemy see (grey lightbulb)aggregator strategy 

 

 

surefire

/surefire

(thumbs up)

maven-surefire.git

 

Kristian Rosenvold 

INFRA-5266

wagon

/wagon

(thumbs up)

maven-wagon.git

 

Olivier Lamy

INFRA-5266

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).

Update the Source Repository page.

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.

(grey lightbulb)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.

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

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, 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 ?

 

  • No labels