StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>First, <a href="http://docs.djangoproject.com/en/dev/releases/1.1-rc-1/" rel="nofollow noreferrer">Django 1.1</a> is <a href="http://www.djangoproject.com/weblog/2009/jul/21/rc/" rel="nofollow noreferrer">one step closer to being released</a>, as <a href="http://www.djangoproject.com/download/" rel="nofollow noreferrer">RC1 is available for download</a>.</p> <p>With that out of the way, I've found some useful things.</p> <ul> <li>If you are planning following this project, you should keep an eye in the <a href="http://docs.djangoproject.com/en/dev/internals/deprecation/#internals-deprecation" rel="nofollow noreferrer">Django deprecation timeline</a>, along the <a href="http://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy" rel="nofollow noreferrer">Django deprecation policy</a>.</li> <li>Another important place to look, is the <a href="http://docs.djangoproject.com/en/dev/misc/api-stability/#misc-api-stability" rel="nofollow noreferrer">API Stability</a> page of <a href="http://docs.djangoproject.com/" rel="nofollow noreferrer">the documentation</a>.</li> <li>Keep an eye on the <a href="http://groups.google.com/group/django-users" rel="nofollow noreferrer">django-users mailing list</a>, as well as the <a href="http://groups.google.com/group/django-developers" rel="nofollow noreferrer">django-developer mailing list</a>.</li> </ul> <p>Am I missing something I should be looking too?</p> <h2>Edit</h2> <p><a href="http://www.djangoproject.com/weblog/2009/jul/29/1-point-1/" rel="nofollow noreferrer" title="Django weblog: Django 1.1 released">Django 1.1 was released</a>!!! You can <a href="http://www.djangoproject.com/download/1.1/tarball/" rel="nofollow noreferrer" title="Download Django 1.1 tarball">download it <strong>right now</strong></a>! :)</p> <p>The question remains if <code>trunk</code> following is not recommended (once upon a time, <em>Django didn't have releases</em>, you only had <code>head</code> of <code>trunk</code>)</p> <hr> <p>Acording to the tech team at <a href="http://www.theonion.com" rel="nofollow noreferrer">The Onion</a>, which <a href="http://www.reddit.com/r/django/comments/bhvhz/the_onion_uses_django_and_why_it_matters_to_us/" rel="nofollow noreferrer">has migrated from Drupal to Django</a>, <a href="http://www.reddit.com/r/django/comments/bhvhz/the_onion_uses_django_and_why_it_matters_to_us/c0mv32r" rel="nofollow noreferrer">Django trunk is extremely stable</a>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload