BowTieXP upgrade information

The BowTieServer is now updated, after a long process of getting this expedited with CGE and despite this being classified as urgent on their end.

I think going forward it would be good to capture a few guidelines between ourselves as a lesson learnt:

Updating the BowTieServer is a lengthy process to get into the queue and can lead to about a day of outage. As such going forward, Ben or myself will request and plan this with CGE in advance. That way we can warn our users about the outage and ensuring it does not affect any workshop / meeting.
New versions of BowTieXP shall not be rolled out to all users until Ben or myself have confirmed this can be done safely (using 3. below). As we intend to rely on communications with BowTieServer more systematically when using XP, this may need to be planned ahead to coincide with the server update.
(BowTieXP and BowTieServer versions are linked whereby upgrading one can prevent them from communicating with each other.)
To allow troubleshooting and version testing before upgrade, new BowTieXP versions shall always be first provided to Ben / myself as a portable file.
(I believe all versions are available as ZIP files which allows us to test functionality / suitability and compatibility with the server without replacing the rolled out version. I think in theory we might even be able to get access to those ourselves, but to comply with IT policies I believe this should come from the IM&T team anyway.)

I think if we follow the above we should be able to avoid major issues of accessibility to our own hosted material or of unplanned outage which may affect our members. Happy to take suggestions on how to improve this too before we can close this ticket.