#11595: Fixture validation errors should report their data
-------------------------------------+-------------------------------------
Reporter: freyley | Owner: raulcd
Type: | Status: assigned
Cleanup/optimization | Component: Core (Serialization)
Milestone: | Severity: Normal
Version: 1.0 | Keywords: easy-pickings
Resolution: | Has patch: 1
Triage Stage: Accepted | Needs tests: 1
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* needs_tests: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
@raulcd -- As described in the
[http://docs.djangoproject.com/en/1.3/internals/contributing/#triage-by-
the-general-community contribution guide] and
[http://docs.djangoproject.com/en/1.3/howto/contribute/#ready-for-checkin
HOWTO], you shouldn't mark your own patch as ready for checkin; that's for
someone else to decide. We like to get at least 2 sets of eyes on a patch
before marking it for commit.
In this case, your patch doesn't have tests, so it can't be ready for
checkin.
--
Ticket URL: <http://code.djangoproject.com/ticket/11595#comment:10>
Django <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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
