At some point, we should consider upgrading CollecTF to run on Django 1.8.
In addition to bug fixes, security updates, etc. the most important new thing in Django 1.8 is migrations. Before 1.8, for changing or removing any existing models, you need to rely on third party tools (we had to use South for a few times, and it isn't very easy to use). Using built-in migrations tool would make any DB changes much easier.
It is not something that we need right now, but it would be nice to have. We can also try to do this while writing tests for CollecTF.
At some point, we should consider upgrading CollecTF to run on Django 1.8.
In addition to bug fixes, security updates, etc. the most important new thing in Django 1.8 is migrations. Before 1.8, for changing or removing any existing models, you need to rely on third party tools (we had to use South for a few times, and it isn't very easy to use). Using built-in migrations tool would make any DB changes much easier.
It is not something that we need right now, but it would be nice to have. We can also try to do this while writing tests for CollecTF.