Beginning in the second half of calendar year 2017, Oracle will be transitioning to a more flexible and responsive strategy for the database software release process. These changes only affect Database and Grid Infrastructure release 12.2 or later.
Overview
Beginning in the second half of calendar year 2017, Oracle will be transitioning to a more flexible and responsive strategy for the database software release process. These changes only affect Database and Grid Infrastructure release 12.2 or later. The primary goals of this strategy are twofold:
1. Embrace a less complex software release process
a. Oracle wants to get new features to market every year instead of waiting several years
b. Oracle desires to improve database release quality by reducing the number of software changes released at one time
b. Oracle desires to improve database release quality by reducing the number of software changes released at one time
2. Provide customers with a more flexible way to both:
a. Efficiently adopt Bug fixes when needed (like the DB Proactive BP currently provides)
b. Efficiently keep current with Quarterly Security Updates once their environment becomes stable (like the PSU currently provides)
b. Efficiently keep current with Quarterly Security Updates once their environment becomes stable (like the PSU currently provides)
To accomplish the goals of this strategy, the following database software changes are being implemented:
Please note that the changes described in this NOTE are only for Database and Grid Infrastructure release 12.2 and beyond. Database version 12.1 and 11.2 will continue to use the legacy PSU/BP process and version numbering systems.
Patching Changes
Beginning with the next Database release (originally designated 12.2.0.2) planned for 2018, new feature releases of the database product will be provided annually, and patchsets will no longer be released. To support both security-related fixes and high-priority non-security fixes to each annual release, quarterly Release Updates (RUs) will be provided each January, April, July and October. To allow customers to keep current on just security-related fixes once their feature environment becomes stable, quarterly Release Updates Revisions (RURs) will be provided each January, April, July and October for the RUs from the past 6 months. This RU and RUR strategy replaces the legacy Patchset Update (PSU) strategy for 12.2.0.1 database software, beginning in July of 2017.
• RUs are proactive, highly tested bundles of critical fixes which enable customers to avoid known issues. They are specific to a particular annual release.
• RURs contain security and regression fixes to a RU that extend the RU’s lifetime up to two quarters. They are specific to a particular RU.
• The legacy terms ‘Patchset’, 'Patchset Update', and 'Database Bundle Patch' will no longer be meaningful for 12.2 database software.
• RURs contain security and regression fixes to a RU that extend the RU’s lifetime up to two quarters. They are specific to a particular RU.
• The legacy terms ‘Patchset’, 'Patchset Update', and 'Database Bundle Patch' will no longer be meaningful for 12.2 database software.
This strategy allows a more conservative approach to maintenance while still getting fast access to critical security and proactive stabilization content. Customers can switch back and forth between RUs and RURs, whereas this is not possible with PSUs and BPs. Both RUs and RURs contain all security fixes, thus eliminating any 'security' versus 'stability' tradeoff.
Figure 1: 12.2.0.1 Database Release - Naming convention for RU/RUR
- Release Update (RU) - Database Release Update 12.2.0.1.<build-date>
- Release Update Revision (RUR) - Database <Quarter> Release Update Revision 12.2.0.1.<build-date>
Lifetime Support Policy for Annual Database Releases
Most annual releases will be supported for 3 years. Periodically, a release will be designated as an "Extended Support Release" and be supported for 8 years. The support life of each release will be documented in the Lifetime Support Policy document.
Release Version Numbering Changes
Beginning in 2018, a new numbering schema for the database software will be implemented. Instead of a legacy nomenclature such as 12.2.0.2, a three (3) field format consisting of: Year.Update.Revision will be used, such as 18.1.0. This will allow clear indication of:
• the annual release designation of the database software
• which quarterly RU (the second field) applies to which annual release.
• which quarterly RUR (the third field) extends which quarterly RU.
• which quarterly RU (the second field) applies to which annual release.
• which quarterly RUR (the third field) extends which quarterly RU.
Disclaimer:
The dates published in this document are for planning and discussion purposes only. It is intended solely to help you plan your I.T. projects. The dates are not a firm development plan. The release and timing of any platforms are subject to change at any time and at Oracle's sole discretion.
Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside of the licensed organization without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
The dates published in this document are for planning and discussion purposes only. It is intended solely to help you plan your I.T. projects. The dates are not a firm development plan. The release and timing of any platforms are subject to change at any time and at Oracle's sole discretion.
Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside of the licensed organization without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
Figure 2: Release and RU Timeline
Please note that the changes described in this NOTE are only for Database and Grid Infrastructure release 12.2 and beyond. Database version 12.1 and 11.2 will continue to use the legacy PSU/BP process and version numbering systems.
Reference - Release Update Introduction and FAQ (Doc ID 2285040.1)
No comments:
Post a Comment