You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.
The move to Django 1.7 moves us away from south to Django's native migration platform. As a result, the avocado migration management subcommand will have to be updated as it relies directly on south to facilitate migrations.
This might be an opportunity to explore more fine grained management or "merges" of metadata from one serialized migration to another depending on the goals of the Harvest road map.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The move to Django 1.7 moves us away from south to Django's native migration platform. As a result, the avocado
migration
management subcommand will have to be updated as it relies directly on south to facilitate migrations.This might be an opportunity to explore more fine grained management or "merges" of metadata from one serialized migration to another depending on the goals of the Harvest road map.
The text was updated successfully, but these errors were encountered: