#8438: porting guide - 0.96 to 1.0
--------------------------------------------------+-------------------------
          Reporter:  daonb <[EMAIL PROTECTED]>  |         Owner:  anonymous
            Status:  new                          |     Milestone:  1.0      
         Component:  Documentation                |       Version:  SVN      
        Resolution:                               |      Keywords:  porting  
             Stage:  Accepted                     |     Has_patch:  1        
        Needs_docs:  0                            |   Needs_tests:  0        
Needs_better_patch:  0                            |  
--------------------------------------------------+-------------------------
Changes (by ramiro):

  * has_patch:  0 => 1

Comment:

 Awesome work guys.

 Do you think there is something else that need to be added to this new
 document or is could be considered complete?

 I'm attaching a patch version of the file with the following changes:

  * Corrected some phrases
  * Added under `docs/releases` (this directory was suggested by Jacob).
 The following two are subject to change:

  * Renamed as `porting-guide.txt`
  * Added a reference to `docs/releases/index.txt`, currently the link is
 located at the bottom of the file.

 NOTE:

  * It would be good if text wrapping is set at 80 characters when
 possible, as the rest of the reST Django documentation.
  * Also, more crossreferencing (classes, settings, tags, would be of grat
 help to the readers.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8438#comment:8>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to