Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X
I don't know if this has been brought up recently but has anyone noticed that since PDMLink 10.1 has been released a maintenance build has been released every 3 or 4 months...except for the next one (M050). M040 was released April 25, 2013 but M050 will be released Q3 2014. About a year and a half? They must finally be putting some work/thoughts into this next build.
Just a hump-day thought.
Steve G
I lived on the "bleeding" edge of Pro/E releases for several years with Pro/E and incrementing Pro/Intralink enough to enable the next build of Pro/E. By keeping up with the build releases, it made it easier to validate changes in release, there weren't as many changes from one build to the next. It should also be mentioned that this was managed with a very tight relationship with PTC and usually very early knowledge of the new feature set.
I have witnessed the other strategy of upgrading on a much less regular basis. What I see is that the workload for evaluating that release is much more tedious because of so many more changes.
Joshua Houser
(have I talked to you about FIRST robotics yet?)
Pelco by Schneider Electric
Methods & Tools Sr. Engineer
Hi All,
Regardless of whether it is ProE or Windchill, there should be a PTC supplied JMeter automated script (currently supported by GSO) to test builds of ProE (like World Car or customer data) and Windchill to go through all/most of the OOTB functionality of the World Car or renamed customer data (ptc-edc*). Thus both performance and OOTB issues with the build can be compared to the previuos recorded baseline. Thus, you can validate you system (mirrored or production) before you release. The script should change much between service packs. I mentioned this to Wil Koler before why isn't this provided by PTC OOTB. This will save so much headaches.
Shouldn't go live until the system is validated with load test and regression test.
That's ITIL's rule or do you do a 80/20.
have a good one,
Patrick
In Reply to Stephen Galayda:
I don't know if this has been brought up recently but has anyone noticed that since PDMLink 10.1 has been released a maintenance build has been released every 3 or 4 months...except for the next one (M050). M040 was released April 25, 2013 but M050 will be released Q3 2014. About a year and a half? They must finally be putting some work/thoughts into this next build.
Just a hump-day thought.
Steve G
Hi All,
I agree with most people who have replied. As soon as a new branch is released (i.e. 10.2), past history and experience with PTC directs me to go to the new version rather than staying on the existing. 10.1 service packs is released slower than 10.2 because I noticemost SPRs and enhancementsare released and tested on 10.2 first then downwardly applied to 10.1.
Yep, it is a question of how much time/risk can the company afford.This is why the risk should be immediately be knownwith an automated test from PTC. I don't know if JMETER can test ProE. I haven't tried Borland SilkTest against ProE.
Patrick
In Reply to Tom Uminn:
I think you're looking at this wrong. 10.1 is old. 10.2 is current and I dare say most developers are either working on later releases of 10.2 or working on 10.3. Maintenance releases for 10.1 will only be released once in a great while to fix really big problems. Based on past history, and what is shown in the product calendar, I doubt 10.1 will go any further than M060.
Tom U.
Hey Dave,
When I was working at the fun company called Comdev great guys like James Deadman, Eugene Stewart, John Smithand Darcy Hodgson, we where allowed to research, architect, play and implement UnionFS andRedHat Linux. I later found a more supported Linux application called AuFS. Architectually, you can install any service pack as a layer ontop of your existing install on a different layer mount. The only problem is this better be on a test database.
You can have a baseline install of Windchill as different mount, then create layered mounts for dev, test and production for different properties and configurations. The same can be done for the vaults. Thus, you don't have to create/use tons of disk for duplicating vaults and Windchill installs. The only duplication is a database.
If the MOR fails just remove the layer of the MOR mount and restore the database. I don't know why people are so afraid of going to Linux. Its so simple once you have it installed and you have no Windows issues and constant reboots/restarts. In the end Linux with AuFS saves so much money in disk space and maintenance support.
Regards,
Patrick
I forgot to mention,
The UnionFS/AuFS mount baseline can be updated at any time by merging or copying over the additional layers to the baselines.
The previous baselines are already archived in backups, once confident, like any code configuration management, reset the baseline mount to a new build/vaulted data.
Cool stuff and not rocket science aye,
Patrick
In Reply to Patrick Chin:
Hey Dave,
When I was working at the fun company called Comdev great guys like James Deadman, Eugene Stewart, John Smithand Darcy Hodgson, we where allowed to research, architect, play and implement UnionFS andRedHat Linux. I later found a more supported Linux application called AuFS. Architectually, you can install any service pack as a layer ontop of your existing install on a different layer mount. The only problem is this better be on a test database.
You can have a baseline install of Windchill as different mount, then create layered mounts for dev, test and production for different properties and configurations. The same can be done for the vaults. Thus, you don't have to create/use tons of disk for duplicating vaults and Windchill installs. The only duplication is a database.
If the MOR fails just remove the layer of the MOR mount and restore the database. I don't know why people are so afraid of going to Linux. Its so simple once you have it installed and you have no Windows issues and constant reboots/restarts. In the end Linux with AuFS saves so much money in disk space and maintenance support.
Regards,
Patrick