document stable schedule snapshots
This commit is contained in:
parent
f500bd6095
commit
0e8d45a408
1 changed files with 5 additions and 0 deletions
|
|
@ -12,6 +12,11 @@ these rules.
|
||||||
- Schedules target whole sets. Users choose an element kind as the assignment
|
- Schedules target whole sets. Users choose an element kind as the assignment
|
||||||
granularity. To schedule a subset, create a separate named set containing
|
granularity. To schedule a subset, create a separate named set containing
|
||||||
that subset.
|
that subset.
|
||||||
|
- Schedules are immutable historical snapshots. Copy the set name and each
|
||||||
|
assignment's name, kind, and full path when creating a schedule.
|
||||||
|
- Persisted schedules must not reference their source set, and persisted
|
||||||
|
assignments must not reference their source elements. Later source edits or
|
||||||
|
deletions must not change an existing schedule.
|
||||||
- Schedule recalculation must preserve completed work while redistributing
|
- Schedule recalculation must preserve completed work while redistributing
|
||||||
unfinished assignments across the remaining dates.
|
unfinished assignments across the remaining dates.
|
||||||
- Planned features in `README.md` are future ideas, not authorized scope.
|
- Planned features in `README.md` are future ideas, not authorized scope.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue