[SCM-1002] create orphaned branches for 2.0-deprecated providers

• Type: Wish
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0-M1
• Component/s: 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
• Assignee: Unassigned
• Reporter: Herve Boutemy
• Created: 09/Oct/22 09:02
• Updated: 16/Oct/22 17:38

Description

proprietary and obsolete (then uneasy to test) providers have been removed in SCM-969 after being deprecated in SCM-953
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

Issue Links

• relates to: SCM-953 Deprecate commercial and CVS providers
• split from: SCM-969 Remove all deprecated (commercial + CVS) providers