Django

Code

Changeset 3728

Show
Ignore:
Timestamp:
09/05/06 11:35:20 (2 years ago)
Author:
ubernostrum
Message:

0.91-bugfixes: changes in the README to provide more useful info on the branch and how it relates to Django proper

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/branches/0.91-bugfixes/README

    r3574 r3728  
    1 Django is a high-level Python Web framework that encourages rapid development 
    2 and clean, pragmatic design. 
     1Django is a high-level Python Web framework that encourages rapid 
     2development and clean, pragmatic design. 
    33 
    4 This is the Django 0.91 "bugfixes" branch, which is intended to provide 
    5 bugfix and patch support for users of Django version 0.91, which was 
    6 the last version before a series of major API changes. No new features 
    7 will be added in this branch, and it is maintained solely as a means 
    8 of providing support to legacy Django installations. If you're just 
    9 starting out with Django, we highly recommend that you use the latest 
    10 stable release or a Subversion checkout from Django's trunk. 
    114 
    12 All documentation is in the "docs" directory and online at 
    13 http://www.djangoproject.com/documentation/0_91/.  If you're just getting started, 
    14 here's how we recommend you read the docs: 
     5About this version 
     6================== 
    157 
    16     * First, read docs/install.txt for instructions on installing Django. 
     8This is the Django 0.90 "bugfixes" branch, which is intended to 
     9provide bugfix and patch support for users of Django 0.90 who have not 
     10been able to migrate to a more recent version. No new features will be 
     11added in this branch, and it is maintained solely as a means of 
     12providing support to legacy Django installations. 
    1713 
    18     * Next, work through the tutorials in order (docs/tutorial01.txt, 
    19       docs/tutorial02.txt, etc.). 
     14If you're completely new to Django we highly recommend that you use 
     15either the latest stable release or a Subversion checkout from 
     16Django's trunk; Django is always evolving, and the latest and greatest 
     17features are only available to users of newer versions of the 
     18framework. 
    2019 
    21     * If you want to set up an actual deployment server, read docs/modpython.txt 
    22       for instructions on running Django under mod_python. 
    2320 
    24     * The rest of the documentation is of the reference-manual variety. 
    25       Read it -- and the FAQ -- as you run into problems. 
     21More information 
     22================ 
    2623 
    27 Docs are updated rigorously. If you find any problems in the docs, or think they 
    28 should be clarified in any way, please take 30 seconds to fill out a ticket 
    29 here: 
     24The complete history of bugs fixed in this branch can be viewed online 
     25at http://code.djangoproject.com/log/django/branches/0.90-bugfixes. 
    3026 
    31 http://code.djangoproject.com/newticket 
     27We also recommend that users of this branch subscribe to the 
     28"django-announce" mailing list, a low-traffic, announcements-only list 
     29which will send messages whenever an important (i.e., 
     30security-related) bug is fixed. You can subscribe to the list via 
     31Google Groups at http://groups.google.com/group/django-announce. 
    3232 
    33 To get more help: 
     33The documentation for this version of Django has been frozen, and is 
     34available online at http://www.djangoproject.com/documentation/0_90/. 
    3435 
    35     * Join the #django channel on irc.freenode.net. Lots of helpful people 
    36       hang out there. Read the archives at http://loglibrary.com/179 . 
    3736 
    38     * Join the django-users mailing list, or read the archives, at 
    39       http://groups-beta.google.com/group/django-users. 
     37Submitting bugs 
     38=============== 
    4039 
    41 To contribute to Django: 
     40If you run into a bug in Django 0.90, please search the Django ticket 
     41database to see if the issue has already been reported; if not, please 
     42head over to http://code.djangoproject.com/newticket and file a new 
     43ticket with as much information about the bug as you can provide. 
    4244 
    43     * Check out http://www.djangoproject.com/community/ for information 
    44       about getting involved. 
     45If you're running into a bug which has been reported but not fixed, 
     46feel free to update the ticket with any additional information you 
     47have, and to assign it to 'ubernostrum' (AKA James Bennett, the 
     48maintainer of this branch). 
    4549