Interesting, but you have to take it in context. That is a planning date, not a commitment. I’m sure the planning date for 12cR1 was at least a year earlier than it was delivered. 🙂
It’s interesting that Oracle would like to have an 18 month release cycle, but we waited about 3 years for 12cR1. Now it looks like 12cR2 is “planned” for about 2.5 years after 12cR1. About 18 months after the release of the 12.1.0.2 patchset.
The standard support policy does not let you skip release 1 this time.
For what I am concerned I read “2016H1/Linux” as not in 2015. And AIX usually half a year later. But I won’t bet on this one, see there how some predications can be wrong : http://www.dba-oracle.com/t_release_dates.htm
Interesting, but you have to take it in context. That is a planning date, not a commitment. I’m sure the planning date for 12cR1 was at least a year earlier than it was delivered. 🙂
It’s interesting that Oracle would like to have an 18 month release cycle, but we waited about 3 years for 12cR1. Now it looks like 12cR2 is “planned” for about 2.5 years after 12cR1. About 18 months after the release of the 12.1.0.2 patchset.
Cheers
Tim…
The standard support policy does not let you skip release 1 this time.
For what I am concerned I read “2016H1/Linux” as not in 2015. And AIX usually half a year later. But I won’t bet on this one, see there how some predications can be wrong : http://www.dba-oracle.com/t_release_dates.htm
