#2901: [patch] Enable admin log display to be restricted to a specific site
------------------------------------------------+---------------------------
Reporter: Christopher Lenz <[EMAIL PROTECTED]> | Owner:
adrian
Status: new | Component: Admin
interface
Version: SVN | Resolution:
Keywords: | Stage: Ready
for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by mtredinnick):
Replying to [comment:2 jacob]:
> This is a good patch, and the get_for_site() method is a great idea. We
probably should wait to apply this until before an actual release to avoid
model breakage midstream, though... I'm not sure what our policy is on
handling things like that.
Don't you mean *just after* an actual release? Otherwise everybody who has
been following svn leading up to the release gets bonus code breakage on
the day of the release (or just before). If we make a backwards-compat
change the day after a release, it will mean that people can stabilise on
the released version until they feel like making the changes, without fear
of missing any intermediate bug fixes (which is the argument against doing
it months after a release).
--
Ticket URL: <http://code.djangoproject.com/ticket/2901#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
