-
Notifications
You must be signed in to change notification settings - Fork 6
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
Republish and add to "newly instrumented" list #74
Comments
The three issues listed above have been addressed. I can go through the process of re-releasing this off of master, but it should have a full QA test, so I thought I'd double check that this is still needed. Also, is there any input as to whether I should publish both phet and phet-io, or just phet-io? It seems like doing both would be good since they'd stay in sync. |
Also, I want to make sure that the phet-io team agrees that this is in a state where it is ready for publication. |
Molarity's recent RC revealed some issues that will need to be fixed before we can proceed with this sim. See phetsims/qa#161 |
@samreid what do you think about a phet-io meeting for this sim. It will be published for accessibility in the coming months, and would be nice to release for PhET-iO when that happens too. |
Sounds great to me as long as our time/schedule permits. Scheduling and timing and priority seem to be a good question for @ariel-phet @kathy-phet and/or @emily-phet. |
I haven't dug too deep on this - there are a lot of issues linked...from my perspective molarity doesn't have a specific timeline. It was awaiting completion of the combobox + all the other things that happen prior to publication. Not sure exactly when we'll get to it. Might be good to have a general conversation about a desired flow for republishing sims with a11y and phet-io. Then when we get a little further down the road, we can see if we can get this alignment to happen for molarity, or perhaps future (other) sims. |
A general conversation can start with https://github.com/phetsims/phet-io/issues/1395. |
This seems stale now. Processes for a11y and phet-io have evolved significantly from when this issue was started. Closing. |
See #67
After #72 we can republish PhET and PhET-iO brands. On hold until #72 done.
The text was updated successfully, but these errors were encountered: