search

phetsims / decaf

PhET Java Simulations converted to HTML5 using CheerpJ
1 stars 0 forks source link

Process for creating RC, production and maintenance releases #49

Open samreid opened 4 years ago

samreid commented 4 years ago

We have no RC build process at the moment, nor do we have a release process. Will we need to deploy maintenance releases? At the moment what is supported is building dev versions. Without building much additional infrastructure, here's what would be easy:

  1. Build and deploy a dev version
  2. Test the dev version as if it is an RC
  3. If that has problems, fix them and deploy a new dev version to treat as RC.2. Compare SHAs to make sure nothing creeps in.
  4. Once RC.x is approved, copy it to the phet website.

I'm not sure how maintenance releases would be done.

samreid commented 4 years ago

One part that we don't have right now is the ability to automatically record versions. At a minimum we need the SHA of decaf, chipper and the SVN revision number.

Also, the version is not reported in the application itself. This sounds like a problem.

Should the build process copy the version info (SHAs, SVN number and semantic version) into the HTML?