Perforce（p4）搁置工作流程？

Question

I'm trying to devise useful workflows for working with p4 shelve. I'm a git user and miss a lot of its features.

The basic flow (store an unfinished changelist, do something else, go back to finish the initial task – the equivalent of git stash) is trivial; I'm looking for tutorials/articles about how to use this feature in more complex scenarios.

Should I give up and use git-p4 or p4sandbox instead?

Answer 1

There's one basic practice widely used in variety of tools - it's sharing changes among people.

1. Share as is - your pending change list will be accessible by others so they could take your delta to re-use

2. Share for review. Eg Code Collaborator uses Perforce shelves as a subject to review.

3. Share for further automation. Eg my company uses P4 pending changelists for taking changes into continuous integration with further submission in case of passing tests.

So basically from git or any other DVCS user point of view, shelves are a weird alternative to branches, there's nothing you can't do with shelves you can do with branches in DVCS.