Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update django to 4.2 #8

Closed
stevenbal opened this issue Mar 4, 2024 · 3 comments
Closed

Update django to 4.2 #8

stevenbal opened this issue Mar 4, 2024 · 3 comments
Assignees
@stevenbal
Labels
enhancement New feature or request

Comments

@stevenbal
Copy link
Contributor

No description provided.

@stevenbal stevenbal self-assigned this Mar 4, 2024
@alextreme
Copy link
Member

Mag opgepakt worden ter voorbereiding op maykinmedia/objects-api#358

stevenbal added a commit that referenced this issue Mar 22, 2024
@stevenbal
⬆️ [#8] Upgrade django to 4.2
4749a08
stevenbal added a commit that referenced this issue Mar 22, 2024
@stevenbal
⬆️ [#8] Upgrade django to 4.2
c9ed79f
stevenbal added a commit that referenced this issue Mar 22, 2024
@stevenbal
Merge pull request #11 from maykinmedia/feature/django-4.2
280082d 
⬆️ [#8] Upgrade django to 4.2
@joeribekker joeribekker added the blocked Issue is blocked. There should be a comment that explains why. label Apr 10, 2024
@joeribekker
Copy link
Member

First, all projects need to migrate. The status is kept in #12

In the future, we might need to use versioning, like:

1.x stays on Django 4.2, and only gets the REALLY important updates
2.x introduces Django 5.2 and all projects can then move to use this.

@joeribekker joeribekker added the enhancement New feature or request label Apr 10, 2024
@stevenbal
Copy link
Contributor Author

open api framework already uses django>=4.2: https://github.com/maykinmedia/open-api-framework/blob/main/pyproject.toml#L30, so I think this issue can be closed

@stevenbal stevenbal removed the blocked Issue is blocked. There should be a comment that explains why. label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevenbal stevenbal

Labels
enhancement New feature or request
Projects
Data en API fundament
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joeribekker @alextreme @stevenbal