CodeInterface samplers dictionary needs to be updated. about raven HOT 4 CLOSED

The unimplemented samplers only raise an error when they try to run, anyway, right? Perhaps we should rethink the classifying process entirely, as I don't think any other code interfaces go through this procedure.

from raven.

Does #181 solve this?

from raven.

I believe so.

from raven.

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or improvement?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements? Does not impact requirements
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. Not a defect
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.) Not a defect
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)? No impact to users
• 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? Not a defect
• 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

from raven.