On Wed, Apr 21, 2010 at 6:01 AM, Kevin Howerton <kevin.hower...@gmail.com> wrote: > Cujo... for starters it's Amon Tobin's first moniker (he remixes jazz > into some delightful tunes, if you don't know of him I strongly > recommend you go to your local record store and pick up a copy of > "Adventures in Foam"). > > Also, I felt it was somewhat apt due to the rabid nature of the > discussions the past few days ... and I think there's a Stephen King > novel of the same name about a dog with rabies or something. > > So we have a clever name ... someone needs to make a rabid, crazy-eyed > pony for the logo and I think we are pretty much done. > > Also, if anyone wants to help with the code ... that would be good too. > > Currently, my main two concerns are this ticket ( > http://code.djangoproject.com/ticket/7539 ... which already has a > working patch I believe) ... and what I perceive is poor exception > handling in templates. > > http://www.bitbucket.org/kevin.howerton/cujo/wiki/Home
Hi Kevin, Great to see someone taking up the challenge of curating a private branch. Although you've described this as a "hostile" branch with no intention of keeping backwards compatibility, I would like to point out that I can't see any reasons the tickets you've identified can't be resolved in a backwards compatible manner. If at all possible (and if you're amenable), I'd like to see the work you do merge back into trunk eventually. Regarding some of the issues you've highlighted: * #7539 has a long history of discussion, but only recently has there been a viable patch. At the time of feature discussion for 1.2, there were still some big issues being sorted out (search django-dev archives for details). I believe many of these issues have been addressed in the most recent patches, but those were only provided in Jan and Feb of this year, well after the feature freeze for 1.2. Looking at the most recent patch, I notice that it doesn't contain any documentation. I suspect there may also be some updates needed following some recent changes to deletion behavior. However, this could easily be something that gets integrated in the 1.3 timeframe if somebody drives the issue. * #2259 has stalled mostly because nobody has been driving it. It's certainly a problem, but there are clearly some issues that need to be resolved. If #2259 is important to you and you want a fix in trunk, those issues will need to be discussed and resolved on django-dev. That said, having a working solution in a branch would be an easy way to kickstart that discussion. * As for exception handling in templates - you won't get any argument from me that error handling is an area that Django could do better. Suggestions and patches welcome. I would also point out that #7539 and #2259 are quite separate issues. If you're doing this work with an eye to delivering work back to trunk, keep in mind that we will need a clean patch that contains *only* the #7539 fixes (or the #2259 fixes) and nothing else. This probably means that you'll need to maintain feature branches internal to your own branch. You may well have a master repository that contains a merge of all your subbranches, but the independent feature-specific branches will be a critical part of managing any feedback to trunk. Best of luck with your branch - once 1.2 is out the door and you have something you'd like to push back to trunk, let us know. Yours, Russ Magee %-) -- 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.
