Re: [aperi-dev] Migrating to Derby 10.3.1.4

[Chris King <chriskng@xxxxxxxxxx>]

My responses below Tom's.
_________________

Chris King
Information Development - Aperi
chriskng@xxxxxxxxxx
Aperi: http://www.eclipse.org/aperi/index.php

Tom Guinane/San Jose/IBM@IBMUS

Tom Guinane/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

10/26/2007 02:32 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	Aperi Development <aperi-dev@xxxxxxxxxxx>
cc
Subject	Re: [aperi-dev] Migrating to Derby 10.3.1.4

Responses below yours... 

Cheers,   Tom
___________________________________________
Tom Guinane     Aperi Project Lead     IBM ARC     408-927-2104     guinane@xxxxxxxxxx     http://www.eclipse.org/aperi/

Todd Singleton/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

10/24/2007 05:08 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	Aperi Development <aperi-dev@xxxxxxxxxxx>
cc
Subject	Re: [aperi-dev] Migrating to Derby 10.3.1.4

Responses below... 

Todd Singleton
Software Engineer, Tivoli, IBM
Menlo Park, CA
email: toddsing@xxxxxxxxxx

Tom Guinane/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

10/24/2007 11:22 AM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	aperi-dev@xxxxxxxxxxx
cc
Subject	[aperi-dev] Migrating to Derby 10.3.1.4

Hi Todd, 
I've got a couple of questions regarding the migration to the next level of Derby, 10.3.1.4, for Aperi.  We have decided we need to go to this level to address some critical bugs.  We are pursuing to get approve from Eclipse legal to bundle.  But, if that does not happen in time, what impact are we imposing on our users?  Actually, I have two questions on this: 

1) What would a new Aperi user experience if they have to manually download and install Derby 10.3.1.4?  Is the installation straightforward? 
TODD> We'd have to test it and determine.  But my thoughts are that it would not be too big of a deal.  It should be very straightforward, simple file replace.  We could also repackage it in the download.   
TOM>> Thanks.  Hans, hopefully we will not have to go down this path, but we need to monitor carefully.
CHRIS >>> Please keep me updated on this process when it is determined. I'll make sure to include it in the installation instructions.

2) What would an existing Aperi user experience if they are migrating from Derby 10.1.2.1 to 10.3.1.4?  Bundled or not, does Derby address upward migration during the install? 
TODD> Not sure if we really need to support this scenario (not sure if we have any crucial deployments).  However, this is a scenario that we would need to test.  But derby would not address migration during installation, no.  It would be a manual process.   
TOM>> Thanks.  Hans, either way, this will have to be addressed in test.
CHRIS >>> We'll also need to document this migration process, most likely in the installation instructions.

Also, are you suggesting that this is a "go".  Should we update the version now?  Are you opening a defect/feature for this?
TOM>> From what I understand, we really do not have much of a choice.  Without the migration we have serious errors.  So, yes, it is a go.  However we do not yet have approval to bundle it.  That is currently in progress and being tracked with IPzilla 1830. 
CHRIS >>> Is there a timetable for this, and will it likely be approved in time to meet the requirments of the R4 schedule?


Cheers,   Tom
___________________________________________
Tom Guinane     Aperi Project Lead     IBM ARC     408-927-2104     guinane@xxxxxxxxxx     http://www.eclipse.org/aperi/_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev