Happy New Year,
So it seems that we didn't get Ca PPM 14.2. even though there has been a lot of discussion about it and it was shown in Ca World.
Will the release be all the way rolled back and when can we expect 15.1. to come out?
If CA sticks to the naming convention where the major number is the year and the minor number is the sequence then apparently as you say D2 release is version 15.1 (or 16.1) and there is no 14.2 version.
Nor can 14.2 be rolled back to anything.
Hyvää uutta vuotta vaan Teillekin.
Talked with support this morning and CA PPM 14.2 has not been released. There is no ETA at this time, nor information about whether it will be 14.2 or 15.1 when it is released.
As said if it was not released in 2014 then it is not 14.2, but 15.1 or 16.1.
Does anyone know as to when 14.2 will be released ? Just out of curiosity
The information we have received from CA is end of March 2015.
I've not heard or seen anything at all. I also wonder if this has any effect on the EOL date of BOXI. When they announced it would be EOL 12/31/15 that essentially gave a year to transition to reports to JasperSoft but we've just about lost a month of that year and still no release.
Dansborg2(14.2) new target release date is end of Q1CY2015 (i.e March 2015)
EOL of BO is still planned for 31 Dec 2015 and yes there are no changes as of now.
Thanks for the info, Nitin - and is it still 14.2, or, would it be 15.1 ?
It is still targeted to be called as 14.2
Sounds like the new version naming convention is abandoned before it is applied even once.?
Could do the same for the product naming and pull Clarity back.
I would vote for your Idea urmas! Hyvä idea
+1! Go on, raise that "Idea" someone!
Kiitos vaan pojat for your support.
I don't believe in ideation. There is no business justification for this.
I think we should all talk to our CA reps and voice our concerns about the EOL time frame ticking away for BOXI. We now are down to 9 months (maybe) to get over to Jaspersoft via 14.2/15.1 (unless you sign up for the extended support). My opinion is that it should be a month for month slip on the BOXI EOL to match the 14.2/15.1 general announcement release. It may be futile, but we should make our voices heard
I heard March as well.
Compare that with the previous change:
BO was introduced in r8.1 in 2008. Actuate support ended in November 2014 with v12.1 SP 3.
CA product team have confirmed they're now targeting March, but it will still be CA PPM 14.2.
There's no change to EOL for BOXI, because that would mean SAP would have to extend support.
To clear up roadmap:
(So that people are not confused by seeing the 14.2 --> 15.1 in this post, there has been no release identified as 15.1 as yet. Confusion is often reduced by referring to a release by its project name, so 14.2 was Dansborg, 14.3 was Eltz, and 14.4 is now known as Armstrong.)
Hope this helps.
You don't say that the naming convention where the major version number is the two digits of the year and the minor version number is sequential starting from 1 for that year was abandoned when the product management changed.
The new or the current version numbering logic has not been disclosed yet.
Retrieving data ...