| 227 | | Short answer: When we're comfortable with Django's APIs, have added all |
|---|
| 228 | | features that we feel are necessary to earn a "1.0" status, and are ready to |
|---|
| 229 | | begin maintaining backwards compatibility. |
|---|
| 230 | | |
|---|
| 231 | | The merging of Django's `Queryset Refactor branch`_ went a long way toward Django |
|---|
| 232 | | 1.0. Merging the `Newforms Admin branch` will be another important step. |
|---|
| 233 | | |
|---|
| 234 | | Of course, you should note that `quite a few production sites`_ use Django in |
|---|
| 235 | | its current status. Don't let the lack of a 1.0 turn you off. |
|---|
| 236 | | |
|---|
| 237 | | .. _Queryset Refactor branch: http://code.djangoproject.com/wiki/QuerysetRefactorBranch |
|---|
| 238 | | .. _Newforms Admin branch: http://code.djangoproject.com/wiki/NewformsAdminBranch |
|---|
| 239 | | .. _quite a few production sites: http://code.djangoproject.com/wiki/DjangoPoweredSites |
|---|
| | 227 | See our `version one roadmap`_ for the detailed timeline. We're aiming for |
|---|
| | 228 | September 2, 2008. |
|---|
| | 229 | |
|---|
| | 230 | .. _version one roadmap: http://code.djangoproject.com/wiki/VersionOneRoadmap |
|---|
