- 08 Nov, 2016 2 commits
-
-
Feanil Patel committed
-
Instead of making the change just for ansible-provision.sh make the change for all ansible runs. Most of them don't currently have this problem right now but I think it makes sense to make them all consistent and not have to worry about this problem in the future.
Feanil Patel committed
-
- 17 Aug, 2016 1 commit
-
-
(cherry picked from commit 8e995343)
Ned Batchelder committed
-
- 15 Aug, 2016 1 commit
-
-
(cherry picked from commit f361f761)
Ned Batchelder committed
-
- 11 Aug, 2016 1 commit
-
-
Ned Batchelder committed
-
- 20 Jul, 2016 1 commit
-
-
Ned Batchelder committed
-
- 08 Jun, 2016 1 commit
-
-
I removed this in 9ae2caa0 so it's a no-op
Kevin Falcone committed
-
- 20 Apr, 2016 1 commit
-
-
Ned Batchelder committed
-
- 11 Jan, 2016 1 commit
-
-
Upgrading to Dogwood is complicated, because we have to make two intermediate stops along the way: once at the end of Django 1.4 to migrate the databases using South, then to the beginning of Django 1.8 to apply --fake-initial migrations. Then we can upgrade to the Dogwood release that we actually want.
Ned Batchelder committed
-
- 18 Jul, 2013 1 commit
-
-
Feanil Patel committed
-
- 27 Jun, 2013 1 commit
-
-
Calen Pennington committed
-