microsoft / microsoft/azure-devops-python-api
Reconsider removing v5 & v6
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 684
- Forks
- 218
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 1
Description
@nechvatalp @nechvatalp Please reconsider how you all have restructured this library. It just broke a ton of our stuff with removing v6 & v5 code. In the old structure the various versions lived side-by-side so I think it's a fair assumption that people used liberal version restrictions assuming that the library would follow that pattern and not suddenly drop v6 from the code entirely.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Review the restructuring that removed the v5 and v6 code, then determine whether side-by-side version support can be restored without breaking existing version restrictions; done means a decided compatibility approach and corresponding implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100