You are currently viewing Steps to follow after fixing an issue and deploying to production

Steps to follow after fixing an issue and deploying to production

I’m going to keep this super short and just cut to the chase.

A lot of developers make the blunder of pushing the fix to production too soon, which causes all sorts of issues. A few of the common mistakes are –

  • Not using pull requests
  • Not testing enough
  • Pushing straight to master

A few good practices (other than not doing what’s listed above) are –

  • Test on development and staging servers before pushing to production server
  • Test all use cases
  • Get it tested by a QA

A bonus step that I implemented in my apps is the popup “A new version is available on the App Store”. So whenever a newer version is available on App Store, the users get this popup when they open the app. Now I do the final testing after updating the app from Store i.e testing it live. And only enabling that update popup once all is ok. Just an extra layer of security to make sure if something unavoidably went wrong at least the users won’t be prompted to update thereby minimising the damage.