django-commons / django-commons/django-enum
Need migration tests that follow django major versions progression.
Open
Nobody has claimed this yet.
tests
- Dominant language
- Python
- Stars
- 110
- Forks
- 6
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Description
For example the constraint issue between 4.2 and 5.
And maybe also different major versions of django-enum.
Contributor guide
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
The issue names no files, existing tests, or entry points. Start by locating the migration test suite and its supported Django-version matrix, then clarify the 4.2-to-5 constraint case and whether django-enum major versions are included. Done means migration tests cover the agreed Django major-version progression and relevant django-enum versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- databases, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100