6.04-01 Back to the Future

This is a technique that reverts the model to a previous revision, allows you to make a fix, sync to Production, and then return Development back to where it was

 

Best Practice article:
Saving incomplete changes during development

Comments

Rule 6.04-01 Back to the FutureThis is a technique that reverts the model back a revision state, allows you to make a fix, sync to Production, and then return Development back to where it was

Use Case:  You are developing a functionality which is not yet complete and Production environment needs an urgent bug fix/hotfix

Here is how it was done in Pre Planual Era: We used to revert the Dev model to previous RT and then do the bug fix and push the changes to Prod

What is wrong with this method?  You lose all the development that you had done since last revision was synced before bug was fixed.

Here is how it should be done in Planual Way:

  1. Add a new revision tag to the development model as a temporary placeholder. (Note the History ID of the last structural change as you'll need it later.)
  2. On the development model, use History to restore to a point where development and production were identical (before any changes were made in development).
  3. Apply the hotfix/bug fix
  4. Save a new revision of the development model.
  5. Sync the development model with the production model
  6. On the development model, use the History ID from Step 1 to restore to the version containing all of the development work (minus the hotfix).
  7. Reapply the hotfix to this version of development.
  8. Create a new revision of the development model

Misbah_1-1602067479393.png

 

 

 

Version history
Last update:
‎11-06-2020 03:12 PM
Updated by:
About the Author
Labels (1)