Controlling the grokking process

Registered by Martijn Faassen on 2007-04-24

We need to be able to control the grokking process a bit better. Certain modules contain code that should only be loaded for testing purposes for instance. These modules should be skipped during the normal grokking process, but loaded when we test the package.

Blueprint information

Status:
Started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Martijn Faassen on 2007-11-08

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.