|
Plastic SCM |
|
Plastic SCM is saying goodbye to stuffy old version control tools that are high on complexity and low on usability. With Plastic SCM every aspect of what you would expect from a configuration management tool has been enhanced. Trace the history of your projects with a number of graphical tools and reports. Use a real relational database designed for speed, stability and scalability for ALL your data and not just metadata. Use a tool that is so smart it will remember if you forget to check something in. And if that's not enough, throw in the fact that it is hands down the best looking SCM tool you will find on the market today.
|
|
|
Graphically Track History (link) It used to be that the only way to track the history of a project was by running lengthy historical reports that spit out all kinds of text, most of which was poorly written comments. Some tools could even represent revision history graphically but with limitations. What we’ve done is going to redefine how users think of revision history. Per-file history can be viewed through a 3D revision tree. This revision tree shows a lot of information, such as the branch each revision descends from, the starting point of each new branch, merge points and label points. The 3D model can be twisted, turned, zoomed in either direction. You can even select two different versions and perform a diff. We allow you to see the revision history of a file across time and across branches literally from every angle. Per-branch history is now visible through the revolutionary branch explorer feature. Branches are displayed as horizontal bar graphs with small squares representing every change (changeset we call it, since all our changes are saved atomically) that you commit. When labels are applied, the changeset displays the labels in our branch explorer. As merges occur, we chart the source and destination of each merge and the resulting merges appear as a new changeset for easy tracking. Also similar to a graph, our horizontal chart shows the date of each change. Put it all together and you can track the evolution of your project across many branches, across time, and across merges easily, simply and quickly. Whether looking at a file or an entire project we have every angle covered. Add in a strong reporting and custom query system, a statistical charting system, (we even track number of line changes!) and you have the most robust set of graphical and reporting tools you will find in any SCM tool. |
Real Relational Database (link) Your most precious resource is your source code. We make no pretentions about our engineering skills, we are pretty darn good but there are database systems out there that are very, very good at storing data - and we use them. Let the database specialists make the best databases while we make the world’s best SCM tool. Why trust your most important asset to anything else? We start with FireBird, a cross-platform, open-source relational database that we use as our default database. FireBird is a trusted database that has been around since 1981, performs very well, and is stable, secure and reliable. It’s a trusted name in relational databases and even offers an ODBC driver for custom queries. If you prefer other databases, no problem! We offer support for MySQL and Microsoft's SQL Server. The best part about our data storage system might be the speed. Unlike every other SCM tool on the market we do not store deltas. I know what you are thinking - that’s just crazy! We are not crazy, actually we are using the database the way it was intended to be used with all the data stored inside and not just metadata - and yes we do sacrifice extra disk space for speed. Our philosophy is, a little extra disk space costs a lot less than wasting your time.
|
|
Replication Does Not Mean Proxy! (link) Why settle for a one-way read-only proxy server to satisfy the needs of your distributed development teams. We offer real data replication. Replication opens a world of possibilities that range from the very simple to the very, very cool. Just imagine that you can implement any one, or all of these scenarios with our Replication feature. Replication for backups: Changes trigger a replication operation which synchronizes data to a backup or roll-over to another server. Replication for performance: Two geographically distributed groups install their own servers and replicate data continuously or through scheduled operations, between locations. No more relying on slow internet connections to get your latest source code, its already in the building. Don’t let other tools fool you with marketing lingo. Replication is read-write in all directions with us, not some read-only proxy server. Of course you can configure one location to be read-only if you want ;) Isn’t it nice to have options? Replication for true distributed SCM: Imagine that every developer has their own server. They can work online or offline. They can work at the office or at home. They can work on anything, at anytime, no matter where, with all the features and tools Plastic SCM has to offer. Your changes can be pushed to a master server at any time while other updates are pulled to your server. You can go so far as to create a network of trusted sources where changes migrate from many people through a few who manage projects or aspects of the project to the master server where the final product is assembled. |
Not Just Cool Looking, Smart Too (link) We might have developed the best looking SCM tool on the market, but that means little if it isn’t also the smartest SCM tool on the market. Our SCM tools allows you to change back and forth between different branches at any given time without checking-in incomplete changes, without first making backups, and without worry because we save your partial changes for you! As you switch from branch to branch we record the state of your development directory and save any changes you made but have not checked in. If you switch to a different branch with different code then your change goes away, and when you switch back your uncommitted changes return. Why is this important and useful? As you work through the day fixing bugs or writing features you can work on many different tasks by switching from one to the other without ever having to change the directory you work out of and without having to commit incomplete changes prematurely. You can work with ease and you can work with confidence because we have you covered from start to finish. What you forget, we remember, and when your boss walks up to you and says, “Drop what you’re doing we have an emergency!!!” you can seamlessly switch between tasks without any concerns about losing your current work. |
|
Don’t Throw Out Those Classics (link) The best of your old favorites are still around. Some of the old standbys are still here. We aren’t trying to re-invent the wheel, just make it a whole lot better. Labels, changesets, branches, ACL security, Active Directory support. These features will appear to you like old familiar friends that have been sent to a day spa and come back looking 10 years younger. This reduces the learning curve when learning the product. And coupled with all the amazing capabilities we are boasting you will find yourself maximizing your SCM potential in no time. You will find integrations into your favorite IDE’s such as Visual Studio, Eclipse and others. We’ve also taken the liberty of integrating with your favorite issue tracking systems such as DevTrack, Jira, OnTime, Bugzilla and Mantis to name a few. In Conclusion The core architecture, graphical versioning, branching, classic features, and beautifully designed user interface all come together in the finest example of engineering and design synergy. Don’t waste another frustrating, confusing and time consuming minute on those other tools. Take a free look at Plastic SCM and see for yourself. |
|
   |
|