Scheduling Ignores Milestones

[RobertII]

When scheduling as late as possible, tasks should be scheduled to complete no later than their milestone. Currently, it seems to be ignored, so that tasks are sometimes scheduled to (start and) finish after their milestone.

Obviously, if the milestone has no date, or a successor has an earlier "latest start date", or a parent has an earlier finish date, then that should take priority.

[ChrisNelson]

I have some major scheduling revisions that I hope to push soon. I believe they will address this concern.

[ChrisNelson]

(In [11419]) Add resource leveling to scheduler. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This is rather naive. It makes sure a resource isn't doing two things
at once but doesn't yet handle priorities when conflicts occur.

[ChrisNelson]

(In [11422]) Add task sorter interface. Refs #9833, #9042, #9290, #9300, #9691, #9784.

[ChrisNelson]

(In [11423]) Add simple task sorter. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This sorts by Trac's built-in priority field (after converting the
priority strings to integers).

[ChrisNelson]

(In [11424]) Implement prioritized scheduling. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This is orthogonal to resource leveling. That is even if resource
leveling is disabled, this schedules the tasks for a resource using the
configured sorting rule.

[ChrisNelson]

(In [11426]) A tree-aware task sorter. Refs #9833, #9042, #9290, #9300, #9691, #9784.

A task's priority depends on its parent's priority.

Includes a base sorter class to hold common sorter methods.

SimpleSorter and ProjectSorter derive from the base class.

(Copy effective priority list, just in case.)

Also remove unneeded debugging output. Refs #9648.

[k3erg]

Just putting myself on the Cc.

I, too, am very much interested in having the tickets scheduled(asap) roughly just by milestone date and ticket estimate (for planning)/finish date(for update scheduling).

This would really help us with planning instead of only documenting. Right now I end up with having tickets way after milestones. I checked out from svn yesterday, so it should be rev. 11441.

If I need correcting with my setup :) or You could use another tester, just let me know.