-
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: Density 1.0.0-dev.11 #507
Labels
QA:dev-test
Dev test before an RC
Comments
Currently high priority (can be done after or in concert with #506) as both are of similar priority to publish |
This was referenced Jun 8, 2020
This was referenced Jun 15, 2020
Current top priority |
This was referenced Jun 17, 2020
This was referenced Jun 17, 2020
bumping down to high priority so #508 can be done first. |
This was referenced Jun 22, 2020
This was referenced Jul 2, 2020
This was referenced Aug 21, 2020
Calling a close to this test, but more tests might be done while other rcs are worked out. |
Can this be closed @jonathanolson? |
Yes, sorry! Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@DianaTavares, @ariel-phet, @kathy-phet density/1.0.0-dev.11 is ready for dev testing. Document issues in https://github.com/phetsims/density/issues and link to this issue.
Assigning @ariel-phet for prioritization.
General Dev Test
What to Test
Focus and Special Instructions
[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested, list them here. Any behaviors you want QA to pay special attention to should be listed here.]
General Dev Test Platforms
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: