Improve D2L version management using version checking
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 16
- Avg merge
- 14d 5h
- Merged PRs (30d)
- 14
Description
See https://docs.valence.desire2learn.com/basic/version.html#checking-for-version-support
After https://github.com/hypothesis/lms/pull/5077 we should be in non-legacy version for the products we use.
It's not enterly clear what the right strategy is that:
- Doesn't auto update to newer versions
- Doesn't reject versions that in theory should be end of live but than in practice work for our propose.
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
Read the D2L version-checking documentation and the changes in hypothesis/lms pull request 5077 first. Define a version-checking strategy that avoids automatic upgrades while retaining versions that work in practice, then document or test the chosen behavior using the relevant integration entry points identified during that review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100