Add 1.5, 1.6 and South timeline entries

Author: benjaoming

content/timeline/2008-08-09-south-0.2.md

@@ -0,0 +1,16 @@
+---
+title: "South 0.2 released"
+date: "2017-12-02"
+draft: false
+
+params:
+  timeline_date: 2008-08-09
+  timeline_type: app
+
+---
+
+Django South 0.2 [is released](https://web.archive.org/web/20080831004106/http://south.aeracode.org/wiki/About). It notably becomes the migration framework for Django for many years (until Django 1.7 is released in 2014). If you were using Django between 2008 and 2014, you most likely also used South:
+
+> Django has always made use of automatic schema generation - the almost-famous "syncdb" that must be run at least once (and often more) on every Django project. If you've ever used Django on a resonably large project, you quickly discover that you're deleting tables and regenerating them if you change schema - and that's only if you're in development, and can afford to possibly lose data.
+>
+> Other frameworks, such as the infamous Ruby on Rails, have migrations, which incrementally build up a schema as a series of migrations are executed, the idea being that a schema change is simply one more migration. South is an attempt to bring migrations over to Django, but in a more robust and useable way.

content/timeline/2012-03-23-django-1.5.md

@@ -0,0 +1,13 @@
+---
+title: "Django version 1.5"
+date: "2017-12-02"
+draft: false
+
+params:
+  timeline_date: 2013-02-26
+  timeline_type: release
+  timeline_release: "1.5"
+
+---
+
+Django 1.5 is released with support for a swappable User model, and the first Django release to support Python 3 (in an experimental way), and `update_fields` is introduced to specify which fields should be saved on a model.

content/timeline/2012-03-23-django-1.6.md

@@ -0,0 +1,13 @@
+---
+title: "Django version 1.6"
+date: "2017-12-02"
+draft: false
+
+params:
+  timeline_date: 2013-11-06
+  timeline_type: release
+  timeline_release: "1.6"
+
+---
+
+Dedicated to Malcolm Tredinnick (RIP), Django 1.6 now officially supports Python 3 and it modernizes the `startproject` and `startapp` commands. Under the hood, persistent database connections are introduced to reuse the same db connection across multiple requests and a call to a Model's `save()` now requires just 1 database query instead of 2.