What does “release xyz does not allow parallel checkout within the release” mean when checking out an object?
Development teams can choose to allow or disallow parallel versions of objects. You will get this message when your release has been set up to disallow parallel versions of objects. For instance, foo.c~1 exists in your working project; another developer has checked out foo.c~2 and is making changes. If your release allows parallel checkout, your checkout of foo.c~1 will result in foo.c~1.1.1 being placed in your working project. If your development team has decided to disallow parallel versions (e.g. don’t allow foo.c~1.1.1 to be created), you will need to wait until: 1. your coworker checks in foo.c~2 2. your coworker completes the task they used to make changes to foo.c~2 3. you do a reconfigure to pick up your coworker’s task (which includes foo.c~2) before you can check out foo.c and make your changes. Of course, another alternative is to allow parallel versions on the release; see the S/CM docs (release command) for more information.
