Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Add roadmap and contributing boilerplate to 1.3 alpha notes.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14517 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 185254a20576edc8dddf6474a7a64855fb15c5b7 1 parent ac25387
James Bennett authored November 11, 2010

Showing 1 changed file with 57 additions and 0 deletions. Show diff stats Hide diff stats

  1. 57  docs/releases/1.3-alpha-1.txt
57  docs/releases/1.3-alpha-1.txt
@@ -331,3 +331,60 @@ and Ctrl-C test termination) have been made redundant. In view of this
331 331
 redundancy, :class:`~django.test.simple.DjangoTestRunner` has been
332 332
 turned into an empty placeholder class, and will be removed entirely
333 333
 in Django 1.5.
  334
+
  335
+The Django 1.3 roadmap
  336
+======================
  337
+
  338
+Before the final Django 1.3 release, several other preview/development
  339
+releases will be made available. The current schedule consists of at
  340
+least the following:
  341
+
  342
+* Week of **November 29, 2010**: First Django 1.3 beta release. Final
  343
+  feature freeze for Django 1.3.
  344
+
  345
+* Week of **January 10, 2011**: First Django 1.3 release
  346
+  candidate. String freeze for translations.
  347
+
  348
+* Week of **January 17, 2011**: Django 1.3 final release.
  349
+
  350
+If necessary, additional alpha, beta or release-candidate packages
  351
+will be issued prior to the final 1.3 release. Django 1.3 will be
  352
+released approximately one week after the final release candidate.
  353
+
  354
+
  355
+What you can do to help
  356
+=======================
  357
+
  358
+In order to provide a high-quality 1.3 release, we need your help. Although this
  359
+alpha release is, again, *not* intended for production use, you can help the
  360
+Django team by trying out the alpha codebase in a safe test environment and
  361
+reporting any bugs or issues you encounter. The Django ticket tracker is the
  362
+central place to search for open issues:
  363
+
  364
+    * http://code.djangoproject.com/timeline
  365
+
  366
+Please open new tickets if no existing ticket corresponds to a problem you're
  367
+running into.
  368
+
  369
+Additionally, discussion of Django development, including progress toward the
  370
+1.3 release, takes place daily on the django-developers mailing list:
  371
+
  372
+    * http://groups.google.com/group/django-developers
  373
+
  374
+... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If you're
  375
+interested in helping out with Django's development, feel free to join the
  376
+discussions there.
  377
+
  378
+Django's online documentation also includes pointers on how to contribute to
  379
+Django:
  380
+
  381
+    * :doc:`How to contribute to Django </internals/contributing>`
  382
+
  383
+Contributions on any level -- developing code, writing documentation or simply
  384
+triaging tickets and helping to test proposed bugfixes -- are always welcome and
  385
+appreciated.
  386
+
  387
+Several development sprints will also be taking place before the 1.3
  388
+release; these will typically be announced in advance on the
  389
+django-developers mailing list, and anyone who wants to help is
  390
+welcome to join in.

0 notes on commit 185254a

Please sign in to comment.
Something went wrong with that request. Please try again.