Hi guys, I was wondering how do you deal with situations where your development branch is having migrations that are NOT part of trunk/current release but that you need to do a migration for a fix in trunk?
Let's say trunk is at migration 2 (on the prod database), but the "super new features" branch is at migration 5 (on the dev database), creating a migration 3 in trunk will create problems when trunk is merged with the "super new features" branch, and doing a migration 6 in trunk will make that migration 3-4-5 won't be executed in prod since prod will already be at version 6. Any solutions? _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
