The inconsistency is unfortunate, there's been some that were released
to PyPI and others that have not :(.
Since 3.3.1, I've started moving towards not pushing release candidates to
PyPI as a standard.
That said, I'm happy to shift towards releasing to PyPI if it gets more
traction in the
Will it be released to PyPI as past release candidates were?
--
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
Hello all,
The django CMS core team just released the first release candidate for
version 3.4.
Download: https://github.com/divio/django-cms/archive/3.4.0rc1.zip
Documentation: http://docs.django-cms.org/en/latest/index.html
Release notes: http://docs.django-cms.org/en/latest/upgrade/3.4.html
Il 30/08/2016 11:19, Jonas Obrist ha scritto:
> Iacopo, please note that I've not released a better-test update yet, so
> my Dj1.10 compat changes are
> on https://github.com/ojii/django-better-test/tree/dj-1.10. Good number
> of tests failing though I have yet to reproduce
> it
Iacopo, please note that I've not released a better-test update yet, so my
Dj1.10 compat changes are on
https://github.com/ojii/django-better-test/tree/dj-1.10. Good number of
tests failing though I have yet to reproduce it
https://travis-ci.org/ojii/django-better-test. I should have time again
Il 30/08/2016 04:14, Jonas Obrist ha scritto:
> Hi everyone,
>
> Over the weekend at PyCon Malaysia I've updated django-classy-tags and
> django-sekizai to 0.8.0 and 0.10.0 respectively.
>
> Both releases only changed Python/Django compatibility.
>
> Both now support:
>
> - Python 2.7, 3.3,
Awesome job man!
--
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"
