On Wed, 5 Jan 2022 at 11:26, Ben Cotton <bcot...@redhat.com> wrote:
>
> https://fedoraproject.org/wiki/Changes/Django4.0
>
> == Summary ==
> Update Django to version 4.0.
>
> == Owner ==
> * Name: [[User:mrunge| Matthias Runge]]
> * Email: mru...@redhat.com
>
>
> == Detailed Description ==
>
> The Django project has regular releases about every 9 months. Django
> 4.0 is a major milestone, and this Change will
> bring the Fedora included version to the latest version.
>
> The immediate step is to bump the python-django package to version
> 4.0. It is expected, that dependent packages will be
> updated as well, or retired, if they haven't seen an update for long time.
>
>
> == Benefit to Fedora ==
>
> This updates to the latest Django version and allows to use the
> distribution provided version to be used both in new developments and
> also with latest Django applications.
>
> The upstream project has more info on what's new
> https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/
>
> The risk of not completing this change is that the next update will be
> more disruptive, Django 4.1 is planned for about the same time as
> Fedora 37 will land.
>
> == Scope ==
> * Proposal owners: python-django will be updated to version 4.0.
> * Other developers:
> Other developers or maintainers will have to test their packages with
> Django 4.0.
> * Release engineering:
> * Policies and guidelines: N/A (not needed for this Change)
> * Trademark approval: N/A (not needed for this Change)
>
> == Upgrade/compatibility impact ==
>
>
> == How To Test ==
> The python3-django package has to be installed in order to run the test.
>
>     django-admin --version
>     4.0
>
>
> == Dependencies ==
> Django (the fedora package name is python-django) has a few dependent
> packages which should get updated (or removed) as noted above. If they
> were not updated for Django 4.0, that probably means that their
> upstream is not very active anymore.
>

Which ones? I think you need to figure out what those dependent
packages are and list them in this change.

>
> == Contingency Plan ==
> * Contingency mechanism: (What to do?  Who will do it?) N/A (not a
> System Wide Change)
> * Contingency deadline: N/A (not a System Wide Change)
> * Blocks release? N/A (not a System Wide Change)
>
> == Documentation ==
>
> Extensive upstream documentation can be found at
> https://docs.djangoproject.com/en/4.0/
>
> --
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis

-- 
Elliott
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to