Development Checklist

[samreid]

• receive artwork for grab bag
• Sim is basically feature complete
• memory leaks and garbage collection
• @samreid should go through the code review checklist, see Developer Code Review Checklist #53
• performance with @jonathanolson, first meeting scheduled for June 14
• Testing a version for AAPT
• Address known issues, cleaning up TODOs
• Make sure fuzz test is passing, see Make sure fuzz tests pass #108
• developer testing, see Developer testing #109
• Design team testing
• some initial dev testing QA, see Initial dev testing #47 and Dev Test: Circuit Construction Kit: DC 1.0.0-dev.135 (and virtual lab) qa#33
• publish a new "prototype" version, see Publish a new version over the "prototype" #46
• code review by @jonathanolson, see Code Review circuit-construction-kit-common#317
• addressing issues raised during code review
• another dev test, see Dev Test: CCK DC 1.0.0-dev.160 qa#48
• QA and address discovered issues

[samreid]

@ariel-phet I would like to confirm the ordering of initial Dev QA testing and initial code review. Do you want to do dev testing first or code review first?

UPDATE: and more generally, would you please review the checklist in this issue description and revise the order if anything is amiss?

[ariel-phet]

@samreid yes, dev testing should occur before code review. Dev testing may well reveal issues that require refactoring/changes. We like to ideally review code that is in a stable state, reasonably bug free, and unlikely to undergo many changes except for those raised by the review.

[samreid]

I published http://www.colorado.edu/physics/phet/dev/html/circuit-construction-kit-dc/1.0.0-dev.160/circuit-construction-kit-dc_en.html and will test it on a few browsers before giving to the QA team.

[samreid]

Since we are on dev testing and hopefully going into RC soon, this issue has served its usefulness, closing.