We utilize Visual SVN for our source code repository. We have a main branch for our suite of applications and currently running PB 2019 R2. We want to start a project to migrate these applications to PB 2022 R2/R3 but at the same time we want to continue working in the main branch in parallel. If we create a branch from the main trunk for PB 2022 R2/R3 migration and once it is complete can we merge back into the main trunk without any issues so after the merge back into the main trunk we will be only working with PB 2022 R2/R3.
The reason I am posing this question is because the merge is happening between PB 2019 R2 PBL's and PB 2022 R2/R3 PBL's which possible have 2 different structures in the source code. We don't want to loose any code changes made in main trunk while the migration branch is being worked on.
- VINOD NAIR
- PowerBuilder
- Wednesday, 29 November 2023 23:24 PM UTC
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.
We are going to try it out with a small test project and see how it works out. I only posted here to see if anyone had any experience with SVN and the 2 versions.
Regards
Vinod