Changes between Version 249 and Version 250 of SprintIdeas
- Timestamp:
- Jun 23, 2008, 5:19:18 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SprintIdeas
v249 v250 1 = This page is getting a major overhaul, please don't edit until this notice is gone = 2 3 ---- 4 5 = What to work on during the Django sprint = 6 7 More than 100 people around the world have signed up for Saturday's Django sprint. What should ''you'' work on, given that so many other people are contributing at the same time? This document attempts to help you answer that question. 8 9 == How to prepare for the sprint == 1 = What to work on during a Django sprint = 2 3 Given that so many other people are contributing to Django, at the same time, during sprints. What should ''you'' work on? This document attempts to help you answer that question. 4 5 == Next upcoming sprint == 6 The next sprint will be the !EuroPython 2008 sprint. This sprint will focus on newforms-admin, read the [http://code.djangoproject.com/wiki/SprintEuroPython2008/ page dedicated to this specific sprint] for further details. 7 8 == How to prepare for a sprint == 10 9 11 10 * Join the [irc://irc.freenode.net/django-sprint #django-sprint IRC Channel]. … … 13 12 * [http://www.djangoproject.com/documentation/install/#installing-the-development-version Install the "trunk" version of Django] (aka the Django development version). 14 13 * [http://www.djangoproject.com/accounts/register/ Create an account in our ticket system]. This will allow you to claim tickets you're working on. 14 * Read the page dedicated to [http://code.djangoproject.com/wiki/SprintIdeas#Nextupcomingsprint this specific sprint]. 15 15 16 16 == What to work on? The short answer == … … 73 73 == Areas requiring caution == 74 74 75 There are a fewareas in Django that are undergoing some fairly major change. Have care if you are wanting to work in the following areas.75 There may be areas in Django that are undergoing some fairly major change. Have care if you are wanting to work in the following areas. 76 76 77 77 === Admin interface === 78 78 79 Joseph Kocherhans is leading the charge to finish the NewformsAdminBranch, which will replace the existing admin code as soon as possible.79 Joseph Kocherhans is leading the charge to finish the NewformsAdminBranch, which will replace the existing admin code. This branch will be merged into trunk within a couple of weeks (probably a week before the [http://code.djangoproject.com/wiki/SprintEuroPython2008 EuroPython2008 sprint]). 80 80 81 81 Consequently, any tickets against the existing admin code that are not real showstoppers and having small impact are unlikely to be applied. We would rather develop the same patch against newforms-admin and fix the problem permanently over there. … … 83 83 By all means, pick some admin tickets to work on. However, read the ticket and try to repeat the problem on newforms-admin. Then write a patch against that branch, rather than trunk. 84 84 85 === Database query construction ===86 87 There are a lot of tickets concerning bad SQL constructs from the ORM. Malcolm Tredinnick is working in the QuerysetRefactorBranch to fix a lot of these. Right now, that branch is not in a usable state for any serious code; large pieces remain to be ported.88 89 Any tickets having to do with SQL constructs will generally be fixed in that branch and merged into trunk. Malcolm has been putting the ''qs-rf'' keyword on tickets that are of this nature. The ''qs-rf-fixed'' keyword is being used for tickets that are fixed on that branch (eventually, all ''qs-rf'' tickets will move to ''qs-rf-fixed'').90 91 If you come across a ticket that looks like a !QuerySet problem and has to do with SQL construction, add that keyword.92 93 85 == Suggestions == 94 86 … … 96 88 97 89 * Whilst working on a task, assign it to yourself so other people know that it's yours. 98 * If you complete a task, edit this page and remove the task 90 * If you complete a task, edit this page and remove the task from this list and add it to the [http://code.djangoproject.com/wiki/SprintIdeas#Results proper results section below] 99 91 * If you make progress on a task and then leave it, edit this page leaving a note of what you've done. 100 92 93 * Any of the '''sprint specific''' goals and tickets: read the page dedicated to [http://code.djangoproject.com/wiki/SprintIdeas#Nextupcomingsprint this specific sprint]. 101 94 * !FormPreview [http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&component=django.contrib.formtools&order=priority and related tickets] 102 95 * Sort out what's happening with limit_choices_to (#1891, #2445, #4046) … … 124 117 Please order by ticket ID. '''Note:''' Don't close the tickets until they've been checked in. 125 118 126 === Results of pycon08 Sprint === 119 === Results of europython08 sprint === 120 121 === Results of pycon08 sprint === 127 122 * #528 Added documentation and improved patch (see [wiki:DjangoSpecifications/Docs/ConvertingRestToOtherFormats wiki page]) 128 123 * #689 (dec 07 sprint work) Updated to trunk as of r7350, fix doctests … … 136 131 * #6832 created with doc patch, to describe decorator-in-URLconf usage and avoid people making #5920 -like errors 137 132 138 === Results of 1stDecember07 Sprint ===133 === Results of 1stDecember07 sprint === 139 134 140 135 * #689 Updated patch with enhancements/fixes by telenieko, apollo13 and ekarulf (documentation, tests, security) … … 185 180 * #6110 added patch and tests to prevent python format on loaddata and dumpdata 186 181 187 188 === Results of September Sprint === 182 === Results of september07 sprint === 189 183 190 184 * #285 (also #1516, #3414) handling SCRIPT_NAME and PATH_INFO in a manner which is mostly correct and mostly consistent across deployment scenarios