Rollback an application to a previous version – then what?

Rollback an application to a previous version – then what?

  


Hi,

I have a question regarding the process of rollback an application to its previous version, as described in document http://www.outsystems.com/help/lifetime/9.1/index.htm#t=User_Stories%2FRollback_to_a_Previous_Version.htm  , in chapter “Create a Tag based on a previous function”.

When you perform this action, the Production environment is again working (version 0.2.1). So for a while the end-users can work, but without the new functionalities that were in version 0.3.

Probably the Development environment is already working on 0.4.

What to do after rollback the Production environment?

Is it just simple to fix the problem in Development version 0.4 and deploy 0.4  to QA and Production? This is possible off course,  but then the users have to wait until version 0.4 arrives in Production.

I can imagine that this is an acceptable situation since the bug is complex (otherwise we could use the hotfix functionality in Lifetime). But I just want to be sure that there is no other way of delivering the fix earlier.  

if it's a blocking production bug, why not simply fix it in the QA directly. test it, and push it towards production.


Then merge the fix with dev?


Yes, that will look like the hotfix solution. 

Are there any limitations on merging a fix to a lower environment? I can imagine e.g. when DB changes or data changes are involved in the solution, lifetime will have a hard time merging.