Feature #173

Implement an update mechanism for the dSS binary

Added by Patrick Stählin over 2 years ago. Updated 7 months ago.

Status:Rejected Start date:10/14/2009
Priority:(P2) High Due date:
Assignee:Patrick Stählin % Done:

0%
Category:-
Target version:0.9.0-alpha1
Severity:Major
Story points-
Velocity based estimate-

Description

Update workflow:

  1. User chooses update on the dSS webinterface
  2. dSS searches for a new binary and a signature in a standard location
  3. User clicks update now
  4. Download binary/signature
  5. Check if the binary matches the signature
  6. Check if the binary runs (e.g. dss.new -v or a config-check)
  7. Move dss.new to dss and exit (provided we have a script that restarts the dSS if it gets killed)

History

#1
Updated by Miguel Rodriguez over 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Johannes Winkelmann
  • Target version set to 0.8.0-alpha1
  • Severity changed from Normal to Major

#2
Updated by Miguel Rodriguez almost 2 years ago

  • Priority changed from (P3) Normal to (P2) High

#3
Updated by Miguel Rodriguez almost 2 years ago

  • Target version changed from 0.8.0-alpha1 to 0.8.0-rc1

#4
Updated by Johannes Winkelmann over 1 year ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Johannes Winkelmann to Patrick Stählin

covered by ipkg

#5
Updated by Patrick Stählin over 1 year ago

  • Target version changed from 0.8.0-rc1 to 0.9.0-alpha1

#6
Updated by Patrick Stählin over 1 year ago

  • Status changed from Resolved to Rejected

Also available in: Atom PDF