Just two small points I'd like to highlight:
On Feb 26, 3:50 am, Russell Keith-Magee <freakboy3...@gmail.com>
wrote:
> I'm not casting blame here. Those doing triage work are doing a great
> job. I'm just pointing out that we have a problem. Despite the best
> efforts of our volunteer triage team, they haven't been able to keep
> up with the backlog. We either need more volunteers to do triage, or
> we need to accept as a community that progress isn't going to be as
> fast as we may like.
More volunteers! Come one people! *SmileyChris blows his triage
trumpet*
> There is also an extent to which Django 1.2 has been the culprit.
> Django 1.2 has been particularly unkind to the ticket queue. The
> feature list for 1.2 is *huge*, and this has meant that smaller issues
> have taken a back seat. For comparison, we made lots of bugfixes
> during the 1.1 development cycle - enough to warrant 1.0.1 and 1.0.2
> point releases. However, during the 1.2 development cycle, there
> really hasn't been enough activity in 1.1.X to warrant us cutting a
> bugfix release.
I concur with Russ' points here, and I like his followon points that
1.3 should have scaled down goals to try and slim down the ticket
backlog.
But I do think it's critical to see a new 1.1 release before 1.2 is
out - if for no other reason than having {% csrf_token %} in a 1.1
official release.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
