Control over update installation

Dean Poirier
Dean Poirier Member Posts: 4 ✭✭
in Proclaim Feedback
There needs to be a way to manage when updates are installed. The forced update on app restart simply does not make sense. For those times where Proclaim crashes, or requires a restart to resolve an issue, I’m always nervous to restart it, because generally, we’re only using the system on the weekends shortly prior to our services. The last thing we need is for an update to force all kinds of changes just before the service.
Tagged:
7
Up
7 votes

Submitted · Last Updated

Comments

  • Dean Poirier
    Dean Poirier Member Posts: 4 ✭✭
    Based on the release of Proclaim 3.1(https://faithlife.com/posts/3083337), the auto update mechanism needs to have some control. Looking at the Proclaim forum, a number of reports indicating that there are critical issues being faced upon updating to 3.1.
    https://faithlife.com/posts/3083841
    https://faithlife.com/posts/3083781 https://faithlife.com/posts/3083628

    I know the team works hard to take care of these issues quickly, but it still makes me nervous as a team leader to potentially have one of my volunteers run into a bug Sunday morning.
  • Jon Hole
    Jon Hole Member Posts: 27 ✭✭
    100%. No production system should automatically update itself. We run Proclaim on production machines that are locked down - which means operators regularly get popups mid-service asking them to log in as an administrator. Please offer an option to turn off automatic updates.
  • Debbie Curry
    Debbie Curry Member Posts: 15 ✭✭
    I agree too.  My rule is no software updates within 24 hours of our service.  Too many changes that could disrupt a service.
  • Jon Hole
    Jon Hole Member Posts: 27 ✭✭
    This is a duplicate:
    https://feedback.logos.com/boards/proclaim/posts/stope-the-mandatory-upgrade

Categories