From 4de6c2f6ef644f42768cb5482ed40e6a4a1f8127 Mon Sep 17 00:00:00 2001 From: Alon Zakai Date: Fri, 9 Dec 2016 11:03:17 -1000 Subject: [PATCH] update process docs --- README.markdown | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/README.markdown b/README.markdown index a396caafb..9c3b7ac4b 100644 --- a/README.markdown +++ b/README.markdown @@ -151,20 +151,19 @@ Release Process Pushing a new build in `builds/ammo.js` should be done only after the following steps: - * Build a safe build and make sure it passes all automatic tests. Safe - builds contain a lot of runtime assertions that can catch potential - bugs (similar to the sort of things valgrind can catch). + * Build using python make.py which generates builds/temp.js - * Build a fast build and make sure it passes all automatic tests. - - * Run closure compiler on that fast build and make sure it passes - all automatic tests. + * Make sure it passes all automatic tests using python test.py + (That uses builds/temp.js by default, you can also pass a flag + saying which build to use.) * Make sure that the stress test benchmark did not regress - compared to the old build. + compared to the old build. That number is printed out at the + end of running the tests. * Run the WebGL demo in examples/webgl_demo and make sure it looks - ok. + ok, using something like firefox examples/webgl_demo/ammo.html + (chrome will need a webserver as it doesn't like file:// urls) Upstream Version