Hello Aubrey It is indeed true that we have lacked support for Aldryn News & Blog due to time restraints on our hand. We are heavily involved into Divio Cloud and have recently upgraded the Core Addons to our latest standards (https://www.django-cms.org/en/blog/2017/02/01/core-addons/). We are also currently working on Django 1.11 support for django CMS 3.4.x (https://github.com/divio/django-cms/pull/5932)
I'm sorry that progress on the essential addons (Newsblog, People, FAQ, Jobs, Events) are lacking and we most likely will not update them until we have introduced 1.11 support. After that we want to upgrade the core addons and switch after that our focus to the essential addons. You are welcome to propose pull request and you can always ping be (FinalAngel) to have a second look or ask the corresponding people for help. Thank You Angelo On Tuesday, 2 May 2017 01:29:30 UTC+2, Aubrey Taylor wrote: > > I'm here because the maintainers at Aldryn Newsblog keep closing issues > requesting support for supported versions of Django. > > Django 1.10 support ends this december, 1.9 ended in April. > > The problem is that Aldryn Newsblog pins to (no greater than) 1.9.x in the > latest version which means its only compatible with an unsupported version > of Django. > > To quote the Aldryn Newsblog docs: > > > Divio is committed to Aldryn News & Blog as a high-quality application > that helps set standards for others in the Aldryn/django CMS ecosystem, and > as a healthy open source project. > > Only supporting a now defunct version of Django seems to contradict this > statement a bit. And I can only imagine users at Divio are unaware that > they are likely running on an-unsupported version of Django if they are > also using Aldryn Newsblog. > > My question is, what is the ETA (if any) for a version of Aldryn newsblog > that at least supports Django 1.10 (though it really should aim at Django > 1.11 support since that is scheduled for LTS). > > Thanks for your time and responses. > > (PS. Issues at the Aldryn Newsblog repo have been opened and subsequently > closed. The maintainers directed the OP here, but I could not find a > matching topic). > > Best Regards, > Aubrey Taylor > > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to django-cms-developers+unsubscr...@googlegroups.com --- 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-developers+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/02d05710-4d87-4e25-a0f7-80f717322bb8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
