1) 10% bug 90% other
I think it's happened only once to be honest. 2) Aside from service packs, we have taken an offline upgrade approach. This typically involves at least one or two failed upgrades for whatever reason. We then make sure we can replicate two or three successful upgrades. That takes anywhere from a week to two weeks if we're able to concentrate on just those tasks. But that's never the case. Preparing for the upgrades involves reading release notes and reconciling a user defined compatibility matrix. That takes a weeks or so. Dedicated, but it ends up being stretched over more time. Lelio --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519-824-4120 Ext 56354 [email protected] www.uoguelph.ca/ccs Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 -----Original Message----- From: cisco-voip [mailto:[email protected]] On Behalf Of Ryan Ratliff (rratliff) Sent: Wednesday, August 23, 2017 9:38 AM To: cisco-voip list Subject: [cisco-voip] UCM Upgrade Poll Quick 2 question poll, feel free to unicast or share your response with the group. 1. When you or your customers have a UCM or IMP upgrade fail, what percentage of failures are due to a bug vs something in the environment (user error, db updates, etc)? % bug: % not a bug: Yes it’s a very subjective question but that’s ok, use your judgement. 2. When an upgrade goes smoothly with no issues, how much time do you put into the planning and preparation for the upgrade (not the execution)? Thanks, -Ryan _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
