On 1/3/07, Robert Myers <[EMAIL PROTECTED]> wrote:
http://code.djangoproject.com/ticket/3217 Currently the tests all pass, but if you look at my test there are a few invalid options which are not being caught. And a few that are not working or cause a different error to occur. I have commented out the expectant errors for all the tests that should fail as a road map to fix them. So the test could be committed to svn as is, then when a paticular bug is fixed the test can be uncommented and verified.
Checked in as [4273].
Here is the roadmap I will follow unless anyone disagrees: 1. Submit tickets for the bugs uncovered by the test in 3217. 2. Submit enhancement ticket to include validation for all admin options. 3. Write unit test for admin context and views to validate the admin options do what they should. 4. Submit any new tickets uncovered by 3 5. Work on patches + uncomment tests to verify results. 6. Offer enhancements to the admin application, with tests (details to follow).
Just about the perfect approach. Fixing bugs and improving testing is a great way to earn brownie points. My only suggestion would be that run your enhancement suggestions past the django-developers group before you start cutting great wads of code reworking the admin app. Patches with large new features are much more likely to be accepted if there has been a little community discussion beforehand.
Time to get to work!
Someone is going to have a busy new year ... :-) 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
