Hi Tim,
On 04/04/2015 06:30 AM, Tim Graham wrote:
> Now that Django 1.8 is released, I wanted to bump this thread for
> discussion so we can hopefully ratify this schedule or modify it based
> on feedback. In particular, I heard a concern that a six month release
> schedule may be too often for th
Hello together,
i'm the author of https://github.com/ierror/django-js-reverse - i'd like to
contribute sth. to django.
Is there e.g. help needed for maintaining the django website? I also have
knowledge in linux / freebsd server hosting.
Best regards from munich,
Bernhard
--
You received this
I'm really curious to know if the version to follow 1.9 is planned to be
2.0 or 1.10. I feel as though 1.x releases have had a lot of major feature
changes. Maybe it's time to start thinking about features in terms of
major, minor, and bugfix/security patch, and start saving major features
for
Hi,
take your pick: https://github.com/django/djangoproject.com/issues :)
Cheers,
Florian
On Monday, April 6, 2015 at 9:38:28 PM UTC+2, Bernhard Ja wrote:
>
> Hello together,
> i'm the author of https://github.com/ierror/django-js-reverse - i'd like
> to contribute sth. to django.
> Is there
Hello,
With the current system of release branches, the release schedule doesn’t
affect much the rhythm at which Django accrues changes. For a given community
of contributors and team of committers, the amount of changes in a new release
is roughly proportional to its development time.
(We cou
On Monday 06 April 2015 23:34:09 Chris Foresman wrote:
> I'm really curious to know if the version to follow 1.9 is planned to be
> 2.0 or 1.10. I feel as though 1.x releases have had a lot of major feature
> changes. Maybe it's time to start thinking about features in terms of
> major, minor, and
With a 9 month schedule, here is what the future might look like:
1.8 - April 2015
1.9 - January 2016
2.0 - October 2016
2.1 - July 2017 (LTS, and might be the last version to support Python 2.7
since 3 years of LTS support would cover until the 2020 sunset.)
2.2 - April 2018
Do you think there
I have a site with a /login URL. This URL is for customer logins to an
ecommerce site, and is distinct from the /admin/login to the Django admin.
However, having upgraded from 1.6 to 1.8, it appears that /admin/login is
getting confused, and running the view associated with the /login URL. Thi
Ignore my silliness... operator error, that the 1.7 change flushed out!
On Apr 6, 2015, at 11:36 PM, Christophe Pettus wrote:
> I have a site with a /login URL. This URL is for customer logins to an
> ecommerce site, and is distinct from the /admin/login to the Django admin.
>
> However, havi
