Release Schedule of Current Database Releases (Doc ID 742060.1)...
Release 12.2: New releases will be annual and the version will be the last two digits of the release year.

The release originally planned as 12.2.0.2 will now be release 18, and the release originally planned as 12.2.0.3 will be release 19. Releases 18 and 19 will be treated as under the umbrella of 12.2 for Lifetime Support purposes. The current plan is for Oracle Database 19 to be the last release for 12.2. This may change in the future to Oracle 20 as the last release for 12.2.
...


---------------------
Liberty is a well-armed lamb contesting the vote!
(С) BENJAMIN FRANKLIN
...
soap: vlejnin mail ру

j2kммм, а если будет два релиза за один год?

насколько я понял, релизов как таковых не будет, Будут обновления два раза в год
RUR (Release Update Revisions)


Release Update and Release Update Revisions for Database Proactive Patch Program (Doc ID 2285040.1)...
Release Updates and Release Update Revisions

To support both security-related fixes and high-priority non-security fixes, 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 most recent two (2) RUs. 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.
• 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>
<Quarter> is 'MMM YYYY'
<build-date> is YYMMDD
...