Hey all!
I'm looking to get some input on your individual processes for reviewing a new version of code and the bugs that are associated with it. The current process that my team and I are using is having Cisco AS perform a "Bug scrub" where they list out all of the known bugs related to a particular version, put it into a pdf, and then review the doc with us and we discuss with them the impact of particular bugs and come to a consensus on whether or not we will move forward with a limited test deployment of the code and then eventually deploy it enterprise-wide.
The current issue that we have with this process is that it takes months at a time to complete and if there is a catastrophic bug in the code we scrap the scrub and move on to the next version, which then takes another few months to complete. Even after we find a version that we decide to move forward with we seem to keep finding new corner case bugs that were not known to that particular version when we reviewed it.
Now this process only applies to our Cisco equipment, which admittedly is far too big of a percentage of our environment but I digress. For other platforms that do not have the arches branded on them we're kind of on our own to review release notes and dig up any related bug information, to which we can then take it to our account team and have them put us in touch with an engineer to answer questions we have.
tl;dr - What sort of process do all of you follow when reviewing new version of code for your routing/switching and other various network platforms?
No comments:
Post a Comment