Typically I've monitored the release cycle on patches to determine how "bad" things were.
In the olden days, Cisco would release a patch when a fixed number of serious issues were resolved. You could then track how many serious bugs were being fixed by the interval between patches. Quicker patches means more issues with a higher severity. If the intervals between patches went down, things were starting to stabilize. So if you saw a patch two months in a row, it might be a "let's wait for the next one." Not sure that will hold true, now that Cisco is saying that "all" releases will be stable-train moving forward for ISE. I see it's been a while from 2.7 to 2.7p1. That could be a good sign. Typically I would wait 2 months before upgrading to make sure there weren't repeated patches. You see this even with some long-lived trains that have patches 8,9,10,11 all very close together. > On Jul 16, 2020, at 2:02 PM, Ciesinski, Nick <[email protected]> wrote: > > ISE 2.7 is a stable release. Cisco released very few new features and instead > focused a lot of bug fixes in 2.6 and 2.7. ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community
