Version 4.3.2 - "Update or not update that is the question"

As a general rule, I update as soon as the release comes out---unless it comes out after a show has opened.  If it is during a run (anywhere from one weekend to four weeks in our house), I read through the release notes and play with it on the off-line editor to see if it fixes bugs or just enhances programming.  I don't want any major changes after training board ops, so I won't update with major releases until between shows, but will update if it doesn't really change the syntax of running the show. 

J. R.

I will update minor tweaks immediately--v 4.3.0 to v4.3.1, for instance.

In instances of a major update--4.2.1 to 4.3.0--I will wait until the schedule slows down and/or other users report in. My venue gets a lot of one-night gigs--single performance concerts w/little-to-no prep or rehearsal time--so if an issue crops up for one night it's a whole client's worth of grief on a tight schedule.  When I went from 4.1.2 to 4.2.0 I had some stability issues, including disabled Backup Sync, so I knocked it back to 4.1.2 and waited for 4.2.1 to come out, which I installed immediately. Thus my updating preferences are based on my own experience, of course--your mileage may vary, probably for the better.

I would like to use my 2nd Congo as a 'tester' for software updates, but it's in a blackbox space with a few dozen static lights so the programming experience isn't the same as the main desk's moving rig.