Make workflow flexible wit Plastic SCM
Rating: 9 out of 10
Use Cases and Deployment Scope
We are developing a big, distributed product for an aviation giant. So the business is complex and so is the technical implementation. A team of 25 people are working on it. So a distributed collaboration is required for systematic development. Plastic SCM is providing us the same environment which is most suitable for our development requirement. It supports the version control for our project and the branching and merging solution for the continuous and simultaneous development. In this way team is able to leverage the best efficiency.
Pros
- Branching
- Merging
- binary freeze or locking
- decentralized behavior
- Efficient for large projects as well, really fast and quick
- Versioning and controlling the repositories
Cons
- No administrative tool, so a lot of manual work need to be done
- Quite often the workspace for Plastic SCM disappears and its weird
- Its not easy to use initially as it requires a knowledge and some efforts
- Its not preferable for the small projects as to set up and use takes a lot of efforts
Likelihood to Recommend
Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously.
Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient
Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient
Vetted Review
2 years of experience