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
Am 20.09.2012 um 21:22 schrieb Pascal Robert prob...@macti.ca:
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
Also, can you use dependencies to mitigate the risk of doing something
incorrectly?
Can you always do migrations in trunk regardless of where the necessity for
them is being created?
On 2012-09-20, at 1:32 PM, Maik Musall wrote:
Am 20.09.2012 um 21:22 schrieb Pascal Robert
Le 2012-09-20 à 16:42, David Holt programming...@mac.com a écrit :
Also, can you use dependencies to mitigate the risk of doing something
incorrectly?
Can you always do migrations in trunk regardless of where the necessity for
them is being created?
The problem is that if the migration
Hi Pascal,
On 21/09/2012, at 4:52 AM, Pascal Robert wrote:
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
--- On Thu, 9/20/12, Pascal Robert prob...@macti.ca wrote:
From: Pascal Robert prob...@macti.ca
Subject: Re: Migrations and dev cycle
To: David Holt programming...@mac.com
Cc: WebObjects Development webobjects-dev@lists.apple.com
Date: Thursday, September 20, 2012, 4:45 PM
Le 2012-09-20
On Thursday, September 20, 2012, Paul Hoadley wrote:
Hi Pascal,
On 21/09/2012, at 4:52 AM, Pascal Robert wrote:
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