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 migr
--- On Thu, 9/20/12, Pascal Robert wrote:
> From: Pascal Robert
> Subject: Re: Migrations and dev cycle
> To: "David Holt"
> Cc: "WebObjects Development"
> Date: Thursday, September 20, 2012, 4:45 PM
>
> Le 2012-09-20 à 16:42, David Holt
> a é
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 migr
Le 2012-09-20 à 16:42, David Holt 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 is adding a non-nu
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 :
>
>> Hi guy
Am 20.09.2012 um 21:22 schrieb Pascal Robert :
> 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 mi
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"