-
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
Dev Test: Charges and Fields [+PhET-iO] #37
Comments
One other point, I think we are trying to get into a pattern where we test the non-phet-io and the phet-io versions and publish them simultaneously. |
To put it in terms of #19, this seems to be the type of phet-io dev test that will be moving on to an RC. |
From #19 (comment) It is assumed, in this case, that all wrappers will be tested. At least one browser per device listed here will be tested.
|
Medium priority until some of the current high priority items finish off (CCK, projectile motion, pendulum lab) |
I published a new dev version as described in phetsims/charges-and-fields#130 (comment) |
Sounds good, let me know when you are ready for the next dev version. |
Next dev versions should include LOL features in joist. |
Closing this issue. iO has changed quite a bit, and this issue is stale. |
In late 2016, Charges and Fields PhET-iO went through an RC for a PhET-iO version, see phetsims/tasks#736
5 issues were raised, 3 of which have been fixed and verified. The remaining 2 issues are:
which are fixed and pending testing.
I noticed that the QA team has several other issues on their radar at the moment, so I was hesitant to create a new dev version now (as noted in https://github.com/phetsims/phet-io/issues/863#issuecomment-322341631 ). The aforementioned issues may be tested in phettest.colorado.edu but before we go to full dev or RC testing, but when the priority/time is right for this issue, let @samreid or @zepumph know and they will create you a dev version on the spot.
Reassigned to @ariel-phet for prioritization, scheduling, delegation and labeling.
The text was updated successfully, but these errors were encountered: