[jira] [Comment Edited] (SCM-1002) create orphaned branches for 2.0-deprecated providers

["Herve Boutemy (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SCM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618280#comment-17618280 ] 

Herve Boutemy edited comment on SCM-1002 at 10/16/22 3:37 PM:
--------------------------------------------------------------

[~michael-o] initial split done on a personal fork: https://github.com/hboutemy/maven-scm/branches
I did not yet try to compile anything nor make the necessary changes, just did the split using a script like the ones used when moving from svn to git: https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/split-scm-providers.sh

do you think it is ok to put these branches to official ASF Git repo?


was (Author: hboutemy):
[~michael-o] initial split done on a personal fork: https://github.com/hboutemy/maven-scm/branches
I did not yet try to compile anything nor make the necessary changes, just did the split using a script like the ones used when moving from svn to git: https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/

do you think it is ok to put these branches to official ASF Git repo?

> create orphaned branches for 2.0-deprecated providers
> -----------------------------------------------------
>
>                 Key: SCM-1002
>                 URL: https://issues.apache.org/jira/browse/SCM-1002
>             Project: Maven SCM
>          Issue Type: Wish
>          Components: maven-scm-provider-accurev, maven-scm-provider-clearcase, maven-scm-provider-cvs, maven-scm-provider-integrity, maven-scm-provider-jazz, maven-scm-provider-monotone, maven-scm-provider-perforce, maven-scm-provider-pvcs, maven-scm-provider-starteam, maven-scm-provider-synergy, maven-scm-provider-tfs, maven-scm-provider-vss
>    Affects Versions: 2.0.0-M1
>            Reporter: Herve Boutemy
>            Priority: Major
>
> less common, uneasy to test, providers have been removed in SCM-969
> the fact that the Maven team itself cannot maintain them does not mean that they should fully disappear: ideally, they should be maintained by dedicated communities which have interest in each SCM, with associated test environments to be able to maintain the code
> to help these communities involve, we can create Git orphaned branches with code history before removal so people can easily start such SCM-oriented projects outside
> if you create such a project, please tell us: we'll link to your project



--
This message was sent by Atlassian Jira
(v8.20.10#820010)