You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We believe it would save a lot of time with maintenance if we had a tool on the server that could tell us the current status and errors with our release branches. Here is our first idea:
This would be a new tool, since it doesn't fit well into the idea of snapshots.
We want these tests:
ReleaseBranch.getStatus()
build/lint/tsc (noting here that lint could potentially because annoying to maintain, but let's start with it in.
Fuzz the built sim. This may lead to a lot of noise, but it would be good to see to start. At its best it could help us see when old releases break on modern browsers. At its worst it could just show us fuzz errors that we have already deemed unimportant and not blocking publication.
The server could have data that could integrate into the current CT report (kinda like CTQ does).
I'm not going to work on this right away, but I'm glad to have an idea, and to be able to crank away at it on the back burner.
The text was updated successfully, but these errors were encountered:
From discussion with @jonathanolson related to phetsims/chipper#983 and #202.
We believe it would save a lot of time with maintenance if we had a tool on the server that could tell us the current status and errors with our release branches. Here is our first idea:
ReleaseBranch.getStatus()
I'm not going to work on this right away, but I'm glad to have an idea, and to be able to crank away at it on the back burner.
The text was updated successfully, but these errors were encountered: