Great question. We haven't had a compelling reason to upgrade to django 3.2 so there are no current plans or roadmap that I'm aware of.
It looks like the EOL for 2.2 security fixes is April 2022 so we definitely need to upgrade by then. Our two main stakeholders (Katello and Galaxy) are both about to release soon so maybe after that (summer/fall) might be a good opportunity to upgrade to 3.2. I think it'd be worthwhile for us to see how much of an impact upgrading 3.2 will have on our codebase. To that end, I've filed this issue: https://pulp.plan.io/issues/8488 Will see if we can look at this soon. David On Wed, Mar 31, 2021 at 1:52 PM Chris Hambridge <chamb...@redhat.com> wrote: > Hi pulp-dev, > > We were discussing upcoming plans for Ansible Automation Platform and one > of the items we touched on was Django upgrade to 3.2 which is the next LTS > release. I wanted to reach out and understand if Pulp had any current > plans/roadmap for a similar upgrade. Given the multiple consumers of Pulp > and plugins for Pulp, I wasn't sure how much additional complexity that may > add. > > Thanks for the info. > > Best, > Chris > > -- > > Chris Hambridge > > Senior Principal Software Engineer > > Red Hat <https://www.redhat.com> > > chamb...@redhat.com > M: 770.365.6343 > @RedHat <https://twitter.com/redhat> Red Hat > <https://www.linkedin.com/company/red-hat> Red Hat > <https://www.facebook.com/RedHatInc> > <https://red.ht/sig> > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://listman.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-dev
