meka at tilda.center
Tue Jun 13 09:56:05 PDT 2017
With the policy of having migrations in 26_to_27 (for the current stable and devel versions) it's hard to work in a team because Django thinks it already has 26_to_27. Do you have a workflow around this or can something be done to improve current situation? Thank you!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the geonode-devel