Hello everyone,
I would like to discuss our current situation regarding software development. We have recently deployed Version 1 of our software to both the UAT and production environments. Now, we are starting to develop Version 2, which we plan to deploy to production within the next 30 days.
I have conducted some research and found a helpful link that provides guidance on branching strategies for low-code development: https://www.outsystems.com/videos/branching-the-way-to-low-code-perfection/
I understand that we can develop and publish our code in our personal areas for review purposes, which will not impact other ongoing work in the development environment. However, if we want to deploy our code to the UAT environment for testing, we will need to merge it into the development environment.
My concern is regarding bug fixing for Version 1. Are there any recommendations for handling bug fixes in this scenario?
Please let me know your thoughts and suggestions.
Hello,
First quest, are you using Reactive or traditional?
As you tag your question with reactive so it is not applicable to publish using personal area in reactive, its valid only for traditional as per Outsystems Documentation
If you can add one more environment to your infrastructure for example Pre-Prod this will help you to develop new phase or version on dev and fix issues on Pre-Prod then deploy from Pre-Prod to production until you finish development and testing of new phase using dev and staging environment then you will need to retrofit all fixes done on Pre-Prod to dev and start your deployment cycle.
The second option which need more attention from developers to do everything on dev (new development and bug fixing) but have a feature flag to disable all new functionalities and screens (for example site property with value true on dev but default value is false and keep it false to other environments)
Thank you for your advice.
Hi Tan.
Yes, It's a pain point we are facing on version handling when working with Outsystems.
As we are doing, any change in Version 1, need to copy and paste by hand to version 2 very very very carefully :D
Regards,
Kiet Phan
You also have the option to move your application from Prod to UAT via Lifetime. So should you need to do an fix in Prod but don't want to do a hotfix you can always overwrite your UAT version with Prod, create the fix in there and then move it back to Prod. You will need to, if applicable, to also create the same fix in Dev as you can't merge that one change into your version 2 app.