Mark,
In a simple word, yes.
The long answer: For PTC's history of version releases (micro and macro) it has always been a nail-biter as to what will happen once the new version goes live. Many, many, many...did I mention many...companies had horrific experiences early on when upgrading major releases. As the build codes climbed the software usually became more stable. That's a given. However, I still deal with companies today that utilize "Once burned" methodology by loading and piloting the new release offline for weeks and months prior to implimentationinorder to mitigate the potential unforeseen landmines.
WF1 was, well let's just forget that one ever existed.
WF2 was better but had it's growing pains and at the end was okay.
WF3 was good out of the box and only got better. By the end of its run was pretty bullet-proof.
WF4 - Something was in the water in Needham at that point in time. Overall it was slower. Something inside was gumming up the works. Early releases crashed a lot. As it grew up it became more stable, not 100%,but still markedly slower than WF3 overall.
WF5 brought it's own baggage to the party. Although stable, the workflow was stunted and drawing ribbon...whew! Screaching halt to productivity for many.
In the immortal words of Mr. F. Gump's mother... Life is a box a chocolates, you never know what you're gonna get.This hold true for our software too.
In Reply to Mark Steffke:
Are people really that afraid to try new datecodes?
