#9261: http://www.djangoproject.com/download/ needs updating
--------------------------------------+-------------------------------------
          Reporter:  kmtracey         |         Owner:  nobody
            Status:  closed           |     Milestone:        
         Component:  Django Web site  |       Version:  1.0   
        Resolution:  fixed            |      Keywords:        
             Stage:  Unreviewed       |     Has_patch:  0     
        Needs_docs:  0                |   Needs_tests:  0     
Needs_better_patch:  0                |  
--------------------------------------+-------------------------------------
Changes (by gwilson):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => fixed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 1. The download page currently mentions the latest micro release as the
 latest official version, so looks like this issue has been resolved.

 2. The text here says that "there will occasionally be backwards-
 incompatible changes," which is still technically valid since our API
 stability documentation says "We’ll only break backwards compatibility of
 these APIs if a bug or security hole makes it completely unavoidable."

 3. Right, the release process documentation states that "Security fixes
 will be applied to the current trunk and the previous two minor releases."
 Currently this would mean trunk, 1.0.X, and 0.96.X.  Looks like this is
 correctly reflected on the download page now.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9261#comment:1>
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 [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