devs perform multiple check-outs from source control, check-in, merge, commit. no different than any other environment. The one thorn is how the current build of architect doesn't monitor file changes to alert you when others make changes to the file your working on. Future builds will no doubt improve the experience.
In a nutshell, you can certainly use architect in a multi-dev source controlled environment today, not perfect but workable. sencha team can speak to future plans.
In a nutshell, you can certainly use architect in a multi-dev source controlled environment today
Thanks for your post, John. Do you have experience working in teams with SA2?
Documentation tells you to export project to .XDA file, share it, import it on the other dev machine, save it as local project, then re-export it to .XDA... This seems to bring lots of overhead to development. I wonder if there is a more efficient way...