Hey Backendless Team!
Collaborative development continues to be really challenging and is a serious concern for scaling our work. It can be very difficult to let everyone on the team know that Person A is working on Page X in a separate dev container and that therefore they should not make any changes in that Page.
I know that a full GIT implementation is a super big ask and not something that will come anytime soon.
BUT, even just having a page checkout / locking mechanism could be REALLY helpful. This would prevent other people on the team from changing a page that is under development in another dev-container or dev-page until the person who is editing it in the other container has ‘unlocked’ it. If small changes are needed then they can coordinate together to unlock and make the changes in both places or something along those lines.
Honestly, it’s still a far cry from the type of version control / merging system that is needed but it would still be a big improvement.
Please let me know your thoughts. I know I’ve talked to a few of you about this previously and it’s generally not felt to be a big issue but I’d say we have some type of code conflict / loss event every other week despite everyone’s best efforts to avoid them.
Thanks!
James