Personally, I look at this query every day, so I'm certainly aware of
what remains to be done...
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&groupdesc=1&group=stage&component=Documentation&has_patch=1&has_patch=0&order=priority
Identifying "low hanging fruit" is
On Mon, Nov 1, 2010 at 4:13 PM, Paul Oswald wrote:
> Some of the issues in that list seem like they would be small patches. Would
> it be possible to have someone mark the low hanging fruit as 1.3?
Yes - go ahead and do it!
We usually spend the last couple-three weeks of each release cycle
push
Is it too late to have the 1.3 Milestone applied to these documentation issues?
http://code.djangoproject.com/ticket/13997
http://code.djangoproject.com/ticket/11185
I'm trying to update some old code that has a custom MultiValueField and
MultiWidget to be 1.2 compatible and I've never made a cu
