ICS 125: How to use Issuezilla

I will set up components, component owners, milestones.
I'll enter defects and issues that I want you to resolve
Start giving tasks to team members by writing (short) issues
When you find a bug: enter an issue, paste in errors, write issue comments, reference the issue number in your CVS commits, resolve the issue for later verification
In your status reports and release notes, reference specific issues for known bugs

You can view a report any time
When you release 1.0.0, all issues with target milestone 1.0.0 must be resolved or moved to a later target milestone.
When you release 1.0.1, all issues with target milestone 1.0.1 must be resolved or moved to a later target milestone.
Change control board rule: Between 1.0.0 and 1.0.1, all CVS changes must mention an issue number in the commit message, otherwise the commit will fail.