-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish a new version over the "prototype" #46
Comments
On hold until #47 is complete. |
@kathy-phet we discussed publishing another "prototype" version once dev testing is complete: #50 (comment) Dev testing is complete, and raised 15 issues, several of which are fixed or non-severe: phetsims/qa#33 @kathy-phet how would you like to proceed with a second "prototype" version? |
Here's a dev version from after dev testing and before code review (in case upcoming code review destabilizes things): |
@kathy-phet said if it is only an hour or so to publish over the prototype, then go for it. Then let @oliver-phet and @kathy-phet know and they can decide if they want to email/etc. I volunteered to do this sometime in the coming week. |
Here's the last place we published the prototype, see #6 |
Proposed version is here: http://www.colorado.edu/physics/phet/dev/html/circuit-construction-kit-dc/1.0.0-dev.157/circuit-construction-kit-dc_en.html I tested a few minutes in firefox and chrome and didn't see any obvious defects yet. |
I followed the script in #6 and published dev.157 as the prototype, and it is now available from the PhET website, see http://phet.colorado.edu/sims/html/circuit-construction-kit-dc/latest/circuit-construction-kit-dc_en.html |
I emailed @kathy-phet and @oliver-phet Full details in #46 The new prototype (dev.157) replaced the old prototype (dev.5) at the same address: Would you like to notify any users or social media about the change? Best Regards, |
@ariel-phet are you working on this too? |
@samreid I already made some social media posts. |
Thanks, closing. |
At Thursday's meeting, it was suggested that we could publish the current CCK on top of the existing "prototype" to get more testing in the wild. This would only be done after a good round of QA.
The text was updated successfully, but these errors were encountered: