p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

We're not going to have an alpha-2, so use those notes as the starting point for the beta notes. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14990 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2010-12-19 15:02:13 +00:00
parent 416ef9aad8
commit 5219bc9f84
2 changed files with 12 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/releases/1.3-alpha-2.txt → docs/releases/1.3-beta-1.txt
View File

@ -1,8 +1,8 @@
================================
Django 1.3 alpha 2 release notes
Django 1.3 beta 1 release notes
================================
Welcome to Django 1.3 alpha 2!
Welcome to Django 1.3 beta 1!
This is the second in a series of preview/development releases leading
up to the eventual release of Django 1.3. This release is primarily
@ -13,8 +13,8 @@ prior to the final 1.3 release.
As such, this release is *not* intended for production use, and any such use
is discouraged.
What's new in Django 1.3 alpha 2
================================
What's new in Django 1.3 beta 1
===============================
Further tweaks to the staticfiles app
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ -103,7 +103,7 @@ and ignored the almost identical implementation in the already used auth app.
A side effect of this duplication was the missing adoption of the changes made
in r12634_ to support a broader set of characters for usernames.
This release refactores the admin's login mechanism to use a subclass of the
This release refactors the admin's login mechanism to use a subclass of the
:class:`~django.contrib.auth.forms.AuthenticationForm` instead of a manual
form validation. The previously undocumented method
``'django.contrib.admin.sites.AdminSite.display_login_form'`` has been removed
@ -119,15 +119,12 @@ Before the final Django 1.3 release, several other preview/development
releases will be made available. The current schedule consists of at
least the following:
* Week of **November 29, 2010**: First Django 1.3 beta release. Final
feature freeze for Django 1.3.
* Week of **January 10, 2011**: First Django 1.3 release
* Week of **January 24, 2011**: First Django 1.3 release
candidate. String freeze for translations.
* Week of **January 17, 2011**: Django 1.3 final release.
* Week of **January 31, 2011**: Django 1.3 final release.
If necessary, additional alpha, beta or release-candidate packages
If necessary, additional beta or release-candidate packages
will be issued prior to the final 1.3 release. Django 1.3 will be
released approximately one week after the final release candidate.
@ -136,8 +133,8 @@ What you can do to help
=======================
In order to provide a high-quality 1.3 release, we need your help. Although this
alpha release is, again, *not* intended for production use, you can help the
Django team by trying out the alpha codebase in a safe test environment and
beta release is, again, *not* intended for production use, you can help the
Django team by trying out the beta codebase in a safe test environment and
reporting any bugs or issues you encounter. The Django ticket tracker is the
central place to search for open issues:
@ -163,8 +160,3 @@ Django:
Contributions on any level -- developing code, writing documentation or simply
triaging tickets and helping to test proposed bugfixes -- are always welcome and
appreciated.
Several development sprints will also be taking place before the 1.3
release; these will typically be announced in advance on the
django-developers mailing list, and anyone who wants to help is
welcome to join in.

2
docs/releases/index.txt
View File

@ -64,7 +64,7 @@ notes.
.. toctree::
:maxdepth: 1
1.3-alpha-2
1.3-beta-1
1.3-alpha-1
1.2-rc-1
1.2-beta-1