Release new version for phet and phet-io brand

[zepumph]

from phetsims/qa#4 (comment), it would be good to do a dev release first. I will do one for phet-io, and then create RC's for the phet and phet-io versions.

I should do these first:

• Centralize slider thumb design for PhET Look and Feel? sun#289 (comment) (use the default thumb with silver)
• bug changes the size of HSlider sun#293 for RIAW before this though.

[zepumph]

After talking with @ariel-phet, we think the best approach to get both a phet-io and phet brand published is to do the following three qa tests:

1. phet brand dev release
2. phet brand rc
3. phet-io rc

[zepumph]

Alright the dev version is ready

[zepumph]

phetsims/qa#16

[zepumph]

Make sure to update credits before publishing

[zepumph]

Issues to tackle before RC:

• The 'R' disappears from formula at max value #28
• [i18n] Equation shifts and panel enlarges #91

[zepumph]

I made some substantial changes in #91, and I will do another dev test before going to RC.

[zepumph]

phet-io dev test: phetsims/qa#32

[phet-steele]

@zepumph don't forget #96 either!

[jessegreenberg]

@zepumph what is the status of this issue? We are ready to deploy a PhET brand RC of this sim with keyboard navigation, should we coordinate?

[zepumph]

I think there is just phetsims/ohms-law#68 (which effects RIAW as well). I would love some help on it, I think it has to do with some layout changes I did earlier in the summer, but I can't track down the problem.

[jessegreenberg]

Ok, thanks @zepumph. Does that need to be fixed before a redeploy? Does the currently deployed version have that issue as well?

[zepumph]

I don't think it is in the latest version on phet. I'll take another look at it and see what I can do.

[zepumph]

phetsims/ohms-law#68 is fixed, and we are ready for a release. I'm not sure if we should do a PhET-iO version now, since there seems to be no request for it. @samreid do you think we should release RIAW for phet-io right now too?

[samreid]

It is up to @kathy-phet.

[samreid]

On second thought, If the sim is improved, it seems we should also test and publish the phet-io one too.

[zepumph]

@samreid how stable do you think master is right now due to https://github.com/phetsims/phet-io/issues/1223. Should we worry?

[samreid]

It still needs attention and should be considered unstable. You could grab an estimate earlier sha or wait unit it is resolved

[zepumph]

I think that resolution sounds like a good idea. I will crank away at some of them, and try to get it more stable so we can figure out if that's the way we want to go definitively.

[zepumph]

@jessegreenberg think that master is more stable now for an RC

[jessegreenberg]

Thanks @zepumph!

[jessegreenberg]

A phetio rc was deployed for testing here:
phetsims/qa#53

Once it passes testing, phet branded version will use the same SHAs.

[zepumph]

Unassigning, let me know how I can help.

[jessegreenberg]

@zepumph in #107 we decided not to include keyboard nav in phet-io releases until a11y features work with PhET-iO. So the current plan is to deploy 1.3-phetio without keyboard nav and then a 1.4 PhET brand version with keyboard nav. Does that sound correct?

[zepumph]

That sounds like our current plan, although it is kinda a pain in the butt. I want to double check with @samreid. Sam does this seem right to you?

[samreid]

Perhaps we should defer further phet-io releases until we get Faraday's Law stabilized and have PhET-iO design meetings for each sim?

[zepumph]

That would be a question for @kathy-phet, using the old way of instrumenting. OL and RIAW are both ready for phet-io releases. The question is should we spend the QA time to do this if we will just need to republish a "stable" version soon.

[zepumph]

@kathy-phet should we proceed with RIAW phet-io release even though it has not had design time to move it to a "stable api?"

[zepumph]

phetio 1.3.0-phetio released!
https://phet-io.colorado.edu/sims/resistance-in-a-wire/1.3.0-phetio/wrappers/index/

[zepumph]

@jessegreenberg you are taking on the phet version in a different issue and a different version (since it has accessibility enabled by default). Closing.