[Django] #26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"

31 views
Skip to first unread message

Django

unread,
Jan 13, 2016, 6:27:20 AM1/13/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
-------------------------------+--------------------
Reporter: guettli | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
On this page https://docs.djangoproject.com/en/1.9/ref/models/meta/
you easily missunderstand the examples provided below
"MyModel._meta.get_fields_with_model():".

I team mate and I just read the source, and not the string above "These
old APIs can be replicated by either:".

I will provide a pull request to make this more clear.

--
Ticket URL: <https://code.djangoproject.com/ticket/26078>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 13, 2016, 6:33:02 AM1/13/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
-------------------------------+--------------------------------------

Reporter: guettli | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by guettli):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0


Comment:

Here is the pull request for meta.txt
https://github.com/django/django/pull/5978

--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:1>

Django

unread,
Jan 13, 2016, 7:03:20 AM1/13/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
--------------------------------------+------------------------------------
Reporter: guettli | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):

* needs_better_patch: 0 => 1
* has_patch: 0 => 1
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted


--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:2>

Django

unread,
Jan 14, 2016, 7:26:06 AM1/14/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
--------------------------------------+------------------------------------
Reporter: guettli | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.9
Severity: Normal | Resolution: fixed

Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):

* status: new => closed
* resolution: => fixed


Comment:

In [changeset:"28acc0d6df844ccfc8de6f4e7d5883eb4841e946" 28acc0d]:
{{{
#!CommitTicketReference repository=""
revision="28acc0d6df844ccfc8de6f4e7d5883eb4841e946"
Fixed #26078 -- Clarified "old vs. new" in model._meta upgrade guide.

Thanks Thomas Güttler for the suggestion.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:3>

Django

unread,
Jan 14, 2016, 7:30:27 AM1/14/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
--------------------------------------+------------------------------------
Reporter: guettli | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.9

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by Tim Graham <timograham@…>):

In [changeset:"f619b72815fd8d0bb6f65921ef07ac4bc8a12e29" f619b728]:
{{{
#!CommitTicketReference repository=""
revision="f619b72815fd8d0bb6f65921ef07ac4bc8a12e29"
[1.9.x] Fixed #26078 -- Clarified "old vs. new" in model._meta upgrade
guide.

Thanks Thomas Güttler for the suggestion.

Backport of 28acc0d6df844ccfc8de6f4e7d5883eb4841e946 from master
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:4>

Django

unread,
Jan 28, 2016, 3:10:52 AM1/28/16
to django-...@googlegroups.com
#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
--------------------------------------+------------------------------------
Reporter: guettli | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.9

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by TZanke):

* cc: tzanke@… (added)


--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:5>

Reply all
Reply to author
Forward
0 new messages