Checkouts explained

As you know, checkout in Plastic is not like "checkout" in CVS or SVN. In fact, the concept is similar to systems like Perforce, Clearcase and such.

So, while checkout means "download" on CVS and its descendants, it means "create a new revision of my element to work with it" on Plastic.

In fact, to download stuff to your workspace you've to use "update" on Plastic.

Ok, once all that is clear, why on earth would you like to have something like a checkout instead of just "checking in" your changes?

Note: Please remember a checkout has nothing to do with a "lock", it doesn't mean you're the only one modifying the file, not at all!

Well, the reason is simple: you let the system know you're working on a new revision which is still "in process" which is very helpful on a variety of scenarios:

Knowing what your colleagues are working on

Create temporary revisions with associated data (watch the screencast below)

Avoid creating ugly temporary files for merge candidates (.mine, .theirs) as you'd do with SVN, CVS...

But, the main topic today is about "shelving your changes" and that's what the next screencast will explain: