My Oracle Support Banner

Siebel CRM Continuous Release Model FAQ (Doc ID 2378034.1)

Last updated on FEBRUARY 08, 2021

Applies to:

Siebel CRM - Version 17.0 [IP2017] to 18.5 [Release V17]
Information in this document applies to any platform.

Purpose

Beginning in April 2018, Oracle has transitioned to a more flexible and responsive strategy for the Siebel CRM innovation releases. These changes only affect Siebel CRM Innovation Pack 2017 release or later. 

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Questions and Answers
 Overview
 Patching Changes - Release Updates and Release Update Revisions
 Release Version Numbering Changes
 Frequently Asked Questions
 Q1: Will Updates be provided on older Siebel CRM releases such as 8.0?
 Q2: If there are no Innovation Packs, will the same new features be included in an Update?
 Q3: When is an Innovation Pack made GA?
 Q4: How do I find out about known issues with Updates and Revisions?
 Q5: What is the lifetime support policy for the new Siebel CRM release model?
 Q6: How existing installations might be impacted?
 Q7: If both Release 18.4 and Release 18.5 are available to download at the start of the project, is the best choice for a customer to always install the latest version?
 Q8: If we are in the process of upgrading to Innovation Pack 2017, should we continue, or go to Release 18.x?
 Q10: So an Update can include optional or mandatory repository changes?
 Q11: Is IRM no longer required when applying Updates?
 Q12: If the Updates are cumulative, and features are optional, are there any recommendations or best practices to understand how to keep the application current?
 Q13: There are no repository changes in 18.4, 18.5 or 18.6?
 Q14: When are repository changes expected to be introduced in an Update? will Updates include mandatory repository changes?
 Q15: How are features optional when applying Updates? what about crucial security bugs?
 Q16: How are schema changes handled when you want to revert back to earlier release?
 Q17: Scenario: When upgrading to 18.x if the latest release available is the 18.4 Update, but during the upgrade process, 18.5 becomes available, should the same type of risk mitigation planning be used that previously went into applying the latest ‘Patch set’ version?
 Q18: Scenario: Will our Testing effort be increased? if an Update includes new functionality then is the effort to apply the Update and test it going to be more than the current approach for applying Patch Sets? With Patch Sets there is limited testing, as they just contain bug fixes. However, if we are adding new/changed functionality into the system as well then this would need more testing.
 Q19: Scenario: We are planning an internal release where we apply the installation of the latest Siebel CRM 'package' only when we need specific fixes/improvement or due to support reasons (DB Support, OS Support…). If we still follow this strategy and for example skip some of your "Updates", then applying the latest one will require more effort (e.g. 18.4 to 18.12). How will this process be easier than the standard annual Innovation Pack upgrade?
 Q20: Scenario: How are 3rd party code changes resolved?, what happens when particular code only works on certain certified platforms? how will customers know what feature works on what certified platform?
 Q21: Scenario: If we do not apply all the contents of an Update, does this mean that our repository and code will be out of synch and therefore increase the risk of future issues and dependencies?
 Q22: How would customers know when and which update will have a new certification?
 Q23: How will we know when a future Update will contain a particular feature?
 Q24: Will 18.4 contain most of new features from SOD?
 Q25: For IP2018, when will bookshelf will be available or the bookshelf will be updated for each Update?
 Q26: Where can we get training on applying Updates and transitioning to the new model?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.