Ticket #1883 (new enhancement)

Opened 8 months ago

Last modified 5 months ago

Upgrade steps presentation and checking

Reported by: gracinet Assigned to: madarche
Priority: P2 Milestone: CPS 3.4.7
Component: CPSCore Version: TRUNK
Severity: normal Keywords:
Cc:

Description

Currently, proposed upgrade steps depend on upgraded version numbers (for the given category, stored on the portal) and checkers (declared functions in the zcml, along the handler).

The rules deduced from that info are obscure, and in particular, the step shouldn't be proposed if the checker returns "false". Could also be convenient to depend on the source version number (to avoid cumbersome code in checkers).

Change History

04/17/08 17:08:18 changed by madarche

To improve the situation we should store in the portal which step have been done.

This would at least clear the situation regarding the fact that not proposed steps are marked as "done". Because there might be steps not proposed that are not done either.