Janitorial code work task for Castor 1.0.4 delivery

Adding all missing JavaDoc tags sound like a job that requires weeks of work if we don't want to add dummy comments to just omit compiler warnings. How do you think of splitting this up into smaller pieces e.g. based on packages. in my opinion it would be best if workload estimate of subtasks would be 1-3 days. If you agree we can rename the subtask you already created. Another task may be to fix failures at current JavaDoc tags.

A general question... when a point release is made, will that be a time to close a super-task and create a new one? Or will a supertask remain open as long as it is valid, with subtasks beneath it that are resolved in different releases?

The supertask may be kept open over some releases and it is not required to resolve all issues that may relate to it. At some point in time we may decide that it is time to close the supertask and create a follow up one.

No straight policy about this one. Ideally, super-taks should be resolved within an assigned release, but somehow it just occured to me that we don't live in an ideal world, do we ? Or is it just me .... . All in all, this is best effort ... true open source style.

We should probably close this task when we deliver 1.0.4 and create a new task to track this sort of work for the next delivery. Thoughts?

Yes, we should ... .