#18018: MessageFailure in Django 1.4 admin
-------------------------------------+-------------------------------------
     Reporter:  Simon                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  reopened
    Component:  Uncategorized        |                  Version:  1.4
     Severity:  Normal               |               Resolution:
     Keywords:  admin, messages,     |             Triage Stage:  Accepted
  failure                            |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by ramiro):

 The [https://docs.djangoproject.com/en/1.4/internals/deprecation/
 deprecation timeline document] says, under the 1.4 section:

   [...] The Message model (in django.contrib.auth) [...] will be removed.
 The messages framework should be used instead. [...] Note that this means
 that the admin application will depend on the messages context processor.

 IMHO adding notes with these kind of caveats to the release notes will
 render that document in a heavy piece and could introduce the risk of
 having manually maintained, duplicate information in two pieces of
 documentation.

 Two different proposals:

 1. Maybe we can add prominent links pointing to the:

    * Deprecation timeline and
    * Latest release notes

    (in that order) for users that are upgrading from previous versions to
 the Installation document
 (https://docs.djangoproject.com/en/1.4/intro/install/#remove-any-old-
 versions-of-django)?

 2. Currently, the main document index has this text in a link: "Release
 notes and upgrading instructions" but the target
 (https://docs.djangoproject.com/en/1.4/releases/) of such link is little
 more than a perfunctor¡y list of release notes documents, there are not
 actual ''upgrading intructions''. Maybe we can add a prominent ''seealso''
 or ''warning'' ReST admonition at the top of such document
 warning/pointing users upgrading from older version that they should read
 the deprecation timeline document.

 Option 1 could be too heavy for a introductory installation document that
 is mostly read by new users. I'd prefer option 2.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18018#comment:11>
Django <https://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.

Reply via email to