Rudder

2011-07-08

18:49 User story #1462 (Rejected): Notifications for the user when a technique is changed with non-structural changes

Sometimes a PT can be updated but doesn't require any action from the user (see #1443 for different cases).
Some o... Jonathan CLARKE

12:46 User story #1455: After a PT lib update, if a policy.xml is not parsable, mark PT as broken

Jonathan CLARKE

12:26 User story #1455 (Rejected): After a PT lib update, if a policy.xml is not parsable, mark PT as broken

After git detects an update in the PT library, if we can't parse a policy.xml file add isBroken=TRUE to that PT-version. Jonathan CLARKE

12:45 User story #1443: When the PT lib is updated, mark PI attached to structurally modified PT as broken

Depriorising this user story as it's a bit of a corner case and seems it will take a lot of time for not a huge value. Jonathan CLARKE

12:40 User story #1445: On technique library update, allow the user to accept the modification

Depriorising this user story as it's a bit of a corner case and seems it will take a lot of time for not a huge value. Jonathan CLARKE