-
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: Natural Selection 1.3.0-dev.1 #573
Comments
Some space appears to be freeing up in QA and this dev test would be a good shake down of a few aspects related to Pan and Zoom. However there are currently several blocking issues noted in the next comment |
Re publishing a dev version... I noted that there are 3 blocking issues. 2 issues are related to PhET-iO support for pan & zoom:
Those issues seem relevant to Natural Selection, given the need to test phetsims/natural-selection#219. 1 issue is related to "key events" (I'm not familiar with this): I contacted @ariel-phet on Zoom. He agrees that these are likely blocking for Natural Selection, and will contact @jessegreenberg . |
This issue should also be tied to this test: phetsims/scenery#1079 |
This issue has been deferred for so long that the issue template has probably evolved, and most (all?) of the above comments are no longer relevant. So I'm going to close this issue, and create a new one for the 1.3.0-dev.1 dev test. |
NOTE: Creation of this dev version is delayed until this issue is in the QA Active Tests list.
@amanda-phet, @ariel-phet, @kathy-phet, @KatieWoe, simulation-name/1.3.0-dev.1 is ready for dev testing. The 1.3 release will be for both phet and phet-io brands, and will involve a full QA cycle. Release plan is documented in phetsims/natural-selection#251.
Document issues in https://github.com/phetsims/natural-selection/issues and link to this issue.
Assigning to @ariel-phet for prioritization.
General Dev Test
What to Test
General Dev Test Platforms
Issues to Verify
These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for
QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.
Link(s)
PhET-iO Dev Test
What to Test
sure the simulation loads without crashing or throwing errors.
General Dev Test Platforms
Issues to Verify
These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for QA
then close the issue if fixed. If ready for review then leave open and assign back to the developer.
Link(s)
FAQs for QA Members
There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.
How should I format my issue?
Here's a template for making issues:
Who should I assign?
We typically assign the developer who opened the issue in the QA repository.
My question isn't in here... What should I do?
You should:
The text was updated successfully, but these errors were encountered: