[SCM-1002] create orphaned branches for 2.0-deprecated providers
- Dominant language
- Java
- Stars
- 104
- Forks
- 189
- Avg merge
- 17h 46m
- Merged PRs (30d)
- 6
Description
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** opened **[SCM-1002](https://issues.apache.org/jira/browse/SCM-1002?redirect=false)** and commented
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
---
**Affects:** 2.0.0-M1
**Issue Links:**
- [SCM-969](https://issues.apache.org/jira/browse/SCM-969) Remove all deprecated (commercial + CVS) providers
(_**"split from"**_)
- [SCM-953](https://issues.apache.org/jira/browse/SCM-953) Deprecate commercial and CVS providers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing SCM-969 and SCM-953, then inspect the repository history around the providers removed there. Identify the pre-removal code and the orphaned branches needed for each provider; done means the branches preserve that history and are made available for dedicated communities to maintain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100