+1 to adopting the Django 2.2 since it's an LTS. We should get a ticket written for it.
In terms of the installer, I think only CentOS current doesn't have 9.6+. I'm working on getting the installer to installer 9.6 via scl on CentOS 7 now and I think I'm almost done https://pulp.plan.io/issues/5147 We also need to document this requirement change (and the mariaDB dropping) in the docs. At some point later we could consider a runtime version check where Pulp refuses to migrate/start if PostgreSQL version < 9.6. On Tue, Jul 23, 2019 at 10:35 AM David Davis <davidda...@redhat.com> wrote: > +1. I wonder how we require a minimum version of PostgreSQL though? Will > that be a documentation change or is there some way to require it > programmatically (e.g. in the pulp 3 installer)? > > David > > > On Tue, Jul 23, 2019 at 10:28 AM Tatiana Tereshchenko <ttere...@redhat.com> > wrote: > >> Any objections to require Django 2.2+? And PostgreSQL 9.6+? >> >> It's not clear yet which Django will be in Centos8 or EPEL 8, if any. >> But I was told by package maintainers that if it's added, then it will >> likely be an LTS version, so Django 2.2 >> https://www.djangoproject.com/download/#supported-versions >> >> One of the nice features 2.2 offers is ignore_conflicts option for >> bulk_create which will be helpful for the migration tool >> https://docs.djangoproject.com/en/2.2/ref/models/querysets/#django.db.models.query.QuerySet.bulk_create >> >> >> >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
