upgrader: refactor dependencies between each steps
This should fix some race conditions which made post-upgrade steps not executed sometimes. * each steps use an defaultActivateParameterDict so that activity they may create inherits the same tag, so that next step also runs after this). This makes it possible for example to use post-upgrade step on documents newly installed in upgrade step. * use tag / after tag between upgrader steps instead of checking if previous alarm had errors. We also now allow force running only one step regardless of the previous step completion state, there was no strong reason to prevernt this. * do not use two different active sense and fix method for alarms, just use an active sense method understanding `fixit` parameter
Showing
Please register or sign in to comment