[SCHEDULER-1080]  Version Locking with ACP
Type Change Request
Priority Low
Severity Trivial
Component Dispatch Scheduler Engine, Setup Package
Fixed In Version [3.6] 3.6
Versions Affected [3.5.3] 3.5.3
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 1/19/2014

Description 
Lock Scheduler 3.6 with ACP 7.1 during installation AND AT RUNTIME.

Comments
1/19/2014 6:50:05 PM   Bob Denny 
Testing under all of the combinations was time consuming. I discovered the problem of the HotFix level this way though.
1/19/2014 6:46:53 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  346
 

 

  Affected files
  /trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/ACPSequencer.cs (Modified)
/trunk/SchedulerSetup/SchedulerSetup.vdproj (Modified)

 

 

  Check-in comment
  Require ACP 7.1.anything and alert into the log ("dead") if not available. THis is the "version locking" logic.
GEM:1080
1/19/2014 6:43:44 PM   Bob Denny 
The locking needs to be such that newer versions of ACP being installed will catch people having old Scheduler installers (and giving a reasonable error). It also needs to be resilient to any ACP hotfix (the third decimal number).