mdeeprose

*** Upgrade Club *** Summer 2016 ***

Discussion created by mdeeprose on Apr 29, 2016
Latest reply on Jan 5, 2017 by chris.bray

The first rule of upgrade club is that everyone talks about upgrade club.

 

I thought it would be useful for everyone doing an upgrade this summer to check in, state what version/platform they are on now, and to what version they plan to upgrade.  Maybe we can find some useful common ground and exploit some synergies?

 

At Southampton we are planning to in-place upgrade from Bb 9.1 April 2014 to Bb 9.1 2015 Q4  We are running a Linux (Redhat 6) platform, and will also upgrade our Oracle database from 11 to 12 (going the standalone route rather than the container model).  We look to be on track to fit in CU1 for 2015 Q4 too.

 

We are going to run two dev servers, one at 2015 Q4 and one at 2016 Q2 and then decide which one best meets our needs in terms of building block compatibility and known issues.  Since we found that TurnItIn have not produced a 2016 Q2 compatible building block in time for summer upgrades we have reluctantly decided that we can only upgrade as far as 2015 Q4.  Note: TurnItIn now have a building block that is compatible with 2016 Q2 (see below) but which unfortunately arrived too late for our upgrade window.

 

We have a downtime weekend arranged for 25/26 June.

 

Who else is planning to upgrade this summer?

 

Matt

 

Message was edited by: Matthew Deeprose - updated our upgrade path to show we will go to 2015 Q4 due to the TurnItIn problems with 2016 Q2.

 

Message was edited by: Matthew Deeprose Added note about TurnItIn building block for 2016 Q2 being released.

Outcomes