Upgrade to Django 4.0.x for F36

[Matthias Runge]

Hey there,

would it be too late to upgrade Django for Fedora 36 to version 4.0.x?
It may require some more package updates, not just Django itself.

The releasenotes are here[1], We have version 3.2 in Fedora 35, which
is a long-term supported release (until 2024)[2].

Unfortunately, I am not able to answer the question of "what would
break?". However, not shipping a newer release would show Fedora as
outdated software.

As hinted in the previous paragraph, I am not involved in any
development connected to Django for some time now. This is a cry for
help. The whole Django stack in Fedora could use more helping hands.
Upstream is very good at providing insights, timelines etc and also
keeps it secured. That also means, there are regular updates.

Matthias


[1] https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/
[2] https://www.djangoproject.com/download/
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;

[Neal Gompa]

On Wed, Jan 5, 2022 at 3:41 AM Matthias Runge <mrunge(a)matthias-runge.de&gt; wrote:
>  Hey there,
>
>  would it be too late to upgrade Django for Fedora 36 to version 4.0.x?
>  It may require some more package updates, not just Django itself.
>
>  The releasenotes are here[1], We have version 3.2 in Fedora 35, which
>  is a long-term supported release (until 2024)[2].
>
>  Unfortunately, I am not able to answer the question of "what would
>  break?". However, not shipping a newer release would show Fedora as
>  outdated software.
>
>  As hinted in the previous paragraph, I am not involved in any
>  development connected to Django for some time now. This is a cry for
>  help. The whole Django stack in Fedora could use more helping hands.
>  Upstream is very good at providing insights, timelines etc and also
>  keeps it secured. That also means, there are regular updates.
>  
It's fine to do. We haven't branched yet. You should file a
Self-Contained Change for it. The deadline for those is January 18.
So, go for it!




--
真実はいつも一つ！/ Always, there's only one truth!

[Matthias Runge]

On Wed, Jan 05, 2022 at 05:19:24AM -0500, Neal Gompa wrote:
>  > As hinted in the previous paragraph, I am not involved in any
>  > development connected to Django for some time now. This is a cry for
>  > help. The whole Django stack in Fedora could use more helping hands.
>  > Upstream is very good at providing insights, timelines etc and also
>  > keeps it secured. That also means, there are regular updates.
>  >
>  
>  It's fine to do. We haven't branched yet. You should file a
>  Self-Contained Change for it. The deadline for those is January 18.
>  So, go for it! 
Done: https://fedoraproject.org/wiki/Fedora_Project_Wiki:Changes/Django4.0

Thanks!
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;

[Neal Gompa]

On Wed, Jan 5, 2022 at 10:10 AM Matthias Runge <mrunge(a)matthias-runge.de&gt; wrote:
>  On Wed, Jan 05, 2022 at 05:19:24AM -0500, Neal Gompa wrote:
>  > > As hinted in the previous paragraph, I am not involved in any
>  > > development connected to Django for some time now. This is a cry for
>  > > help. The whole Django stack in Fedora could use more helping hands.
>  > > Upstream is very good at providing insights, timelines etc and also
>  > > keeps it secured. That also means, there are regular updates.
>  > >
>  >
>  > It's fine to do. We haven't branched yet. You should file a
>  > Self-Contained Change for it. The deadline for those is January 18.
>  > So, go for it!
>
>  Done: https://fedoraproject.org/wiki/Fedora_Project_Wiki:Changes/Django4.0
>  
Uhh, I think something is wrong here. How did this article get
namespaced like that? Maybe Ben could help fix it if you don't know
how that happened...



-- 
真実はいつも一つ！/ Always, there's only one truth!

[Ben Cotton]

On Wed, Jan 5, 2022 at 10:12 AM Neal Gompa <ngompa13(a)gmail.com&gt; wrote:
>  Uhh, I think something is wrong here. How did this article get
>  namespaced like that? Maybe Ben could help fix it if you don't know
>  how that happened... 
Fixed.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis

[Matthias Runge]

On Wed, Jan 05, 2022 at 10:17:29AM -0500, Ben Cotton wrote:
>  On Wed, Jan 5, 2022 at 10:12 AM Neal Gompa <ngompa13(a)gmail.com&gt;
> wrote:
>  >
>  > Uhh, I think something is wrong here. How did this article get
>  > namespaced like that? Maybe Ben could help fix it if you don't know
>  > how that happened...
>  
>  Fixed. 
Thank you.
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;

[Karolina Surma]

Hey Mattias,

On 1/5/22 09:39, Matthias Runge wrote:
>  Hey there,
>  
>  would it be too late to upgrade Django for Fedora 36 to version 4.0.x?
>  It may require some more package updates, not just Django itself.
>  
>  The releasenotes are here[1], We have version 3.2 in Fedora 35, which
>  is a long-term supported release (until 2024)[2].
>  
>  Unfortunately, I am not able to answer the question of "what would
>  break?". However, not shipping a newer release would show Fedora as
>  outdated software. 
I can help you with assessing the impact, we do this routinely as a part
of update workflow in the Python-maint team.

The idea is to discover which packages depend on your package in the
build time and then rebuild them on top of the changed package.
For that, we use Copr.
The process is described here (it may be a bit obscure for people not
familiar with Copr): https://hackmd.io/81DXky5lRj-cUiSTeiag2A?view

Feel free to reach me off list if you'd like any help with that.


Those are packages that require python3-django in the build time:

$ repoquery --repo=rawhide{,-source} --whatrequires python3-django
--recursive | grep src$ | pkgname | sort | uniq
ara
bodhi
monkeytype
python3-openid
python-authlib
python-django-allauth
python-django-appconf
python-django-auth-ldap
python-django-configurations
python-django-contrib-comments
python-django-debreach
python-django-extensions
python-django-filter
python-django-formtools
python-django-gravatar2
python-django-haystack
python-django-ipware
python-django-mailman3
python-django-markdownx
python-django-picklefield
python-django-prometheus
python-django-pyscss
python-djangoql
python-django-redis
python-django-uuslug
python-environs
python-hypothesis
python-livereload
python-odata-query
python-opentelemetry
python-pyscaffold
python-pytest-django
python-shortuuid
python-whitenoise

And there are also packages that pin Django to version lower than 4.x -
those will stop building after the update and it would be good to work
with the respective upstreams to have it unpinned on time.

$ for pkg in $(repoquery -q --repo=rawhide{,-source} --whatrequires
python3-django); do repoquery -q --repo=rawhide{,-source} --requires
$pkg | grep -E '\bdjango\b' | grep '<' && echo -e
"${pkg}\n"; done

(python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2)
hyperkitty-0:1.3.5-1.fc36.noarch

(python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2)
postorius-0:1.3.6-1.fc36.noarch

(python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2)
python3-django-mailman3-0:1.3.7-1.fc36.noarch

(python3.10dist(django-picklefield) < 4~~ with
python3.10dist(django-picklefield) >= 3.0.1)
python3-django-q-0:1.3.9-2.fc36.noarch



Karolina

>  
>  As hinted in the previous paragraph, I am not involved in any
>  development connected to Django for some time now. This is a cry for
>  help. The whole Django stack in Fedora could use more helping hands.
>  Upstream is very good at providing insights, timelines etc and also
>  keeps it secured. That also means, there are regular updates.
>  
>  Matthias
>  
>  
>  [1] https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/
>  [2] https://www.djangoproject.com/download/