On Sat, Sep 13, 2014 at 2:55 PM, Robert Scholte <[email protected]> wrote:
> http://markmail.org/thread/owemhec7vfjdnvhc > > IIRC the bottom line is that some parts are hard to migrate. > For instance: we prefer to keep the plugins together, but if it's 1 repo > per release-cycle project, we need a huge number of separate repo's. > For the maven-release project, as being one of the most active developers > on this project I didn't had the need to move it. Subversion works fine for > me. However, it's an isolated project, so it is a good candidate *if* we > want to move it. > Since scm is in git already, avoiding moving does not protect us from bootstrap problems. I see some irony in the fact that the bug I'm trying to resolve, MRELEASE-875, is all about having multiple releasable units in one repo. According to https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration, release is suppose to migrate! > thanks, > Robert > > > Op Sat, 13 Sep 2014 18:10:28 +0200 schreef Benson Margulies < > [email protected]>: > > Since I'm planning a release, it occurs to me that this would be a >> convenient moment to move this project. Did we decide to just migrate >> things like this with no further discussion, or do we decide one by one? >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
