On 23/01/2015 20:53, Tim Graham wrote:
> Could you give some ideas behind the thinking that it's too soon to drop
> 1.6 support? For example, if a project wants to use Django 1.6 why can't
> they stick with django-cms 3.0.X? Do you find that upgrading django-cms
> on your projects is much easier than upgrading Django? I didn't see any
> planned release dates on the django-cms roadmap [1] so obviously that
> would affect this decision.
>
> As you know, I've been working on patches to cleanup django-cms from
> when it supported more than two version of Django. This is quite a lot
> of effort (first introducing the shims and then removing then) and I'm
> wondering if it's a path the team wants to down again? As Django 1.8 is
> the next LTS, my idea would be to designate some version of django-cms
> as a matching LTS, but on the "develop" branch, don't try to maintain
> compatibility with all versions of Django until Django's next LTS.
>
> I'm curious to get feedback on this idea and would be happy to dialog
> more on it. Alternatively, I am thinking maybe we should alter Django's
> own LTS policy in some way so that third-party packages like django-cms
> don't end up in this situation of needing to support more than 2 version
> of Django.
>
>
https://github.com/divio/django-cms/wiki/Roadmap
Views expressed here are just my own, as there hasn't been any formal
discussion on the technical board on this topic.
django CMS 3.1 is a stability release due in a couple of months (see
https://github.com/divio/django-cms/milestones) that aims to improve the
overall experience with django CMS 3 and tackle issues that cannot be
solved in 3.0.x branch (as the concurrency issues caused by mptt).
Upgrade to 3.1 will be (hopefully) painless (the two deprecated features
that's going to be removed have a clear upgrade path with very little
changes in custom code).
Django 1.7 brought in-core migrations, which is a huge step ahead and is
a fundamental goal to improve the Django ecosystem, however 1.6 / south
is still widely adopted, and 1.6 -> 1.7 upgrade it's not an easy task,
especially in large projects.
Given the scope and timing of django CMS 3.1 I think we should really
try hard to avoid removing Django 1.6 support.
>
> On Friday, January 23, 2015 at 7:35:37 AM UTC-5, yakky wrote:
>
> Il 22/01/2015 18:22, Tim Graham ha scritto:
> > Django 1.8 is scheduled to be released in about 2 months at which
> point
> > 1.6 will no longer be supported. If I worked on a branch to add 1.8
> > support and drop 1.6 support would be it accepted to merge around
> the
> > time 1.8 is released? Since features deprecated in 1.6 are
> removed in
> > 1.8, it will be easier if we don't have to support more than two
> > versions of Django.
> >
>
> I don't think we can drop 1.6 support so soon.
> I already investigated preliminary 1.8 support, but currently we need
> some upstream package update to make it work on 1.8 (hvad being the
> most
> important: django CMS itself does not depend on hvad, but the testsuite
> does).
>
> --
>
> Iacopo Spalletti
>
> --
> You received this message because you are subscribed to the Google
> Groups "django CMS developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
django-cms-devel...@googlegroups.com
> <mailto:
django-cms-devel...@googlegroups.com>.
> For more options, visit
https://groups.google.com/d/optout.
--
Saluti
Iacopo Spalletti