Herbert, all,
I received a lot of direct messages, and it seems that my message was probably not clear enough, and probably scared some of you.
Two years ago we went from 8.0 to 9.0 without enough tests and discovered bugs after golive, bugs that would have been easily found with enough testing with the correct people.
My message was just a warning for people about to move to 10.0 to be sure that their scope is operational in this MOR.
If you're using Windchill only for CAD data management you will be fine, but if you plan to use others features of Windchill you need to check.
For example :
ACL : Mike early talked about CS31715 If one has preference Latest Version Search = Yes and that user does not have Read for the Latest Iteration of the Latest Revision, the system returns no search results.
Solr : CS28264 Solr keyword search may not give any result if two keywords are using wildcards
ESI : SPR 2092747 Contributing content link created between a WTPART and a CadDocument will not be collected by ESI for publishig
We are about to move to 9.1 to 10.0 in August 2012 and so are deeply testing Windchill 10.0 with our key users prior to go live.
When moving from one version of Windchill to another one and using a large scope of Windchill features, it is intended to raised issues.
Linus Torvalds said "Nobody actually creates perfect code the first time around, except me. But there's only one of me".
A software is never bugfree, as comparison I just had a look at metalink and see that Oracle released 3 patches that covered 7 bugs since this Monday just for 11.1.0.7 version.
Many bugs that we have opened since F000 are fixed in M020, and the remaining one will be fixed in M030, which generally starts to be a mature version in Windchill (9.0 M050, 9.1M040).
With our target in 10.0 M030 I'm confident that our golive will be successful next summer.
Cheers,
Morgan