it will predominantly store).
And of course, if you get code delivered from any of those third parties, you probably want to version it along with the delivered binaries unless the binaries can be reproduced from the code you were given (sometimes the source delivered is insufficient for that).
If you have to modify any of that code from the third-party for your own custom, value-added purpose, you will probably want to use the Third Party Codeline pattern (plus, get them to incorporate your changes, unless the organization deems them proprietary and is unwilling to submit them back to the vendor).
-  Object Solutions: Managing the Object-Oriented Project , by Grady Booch; Addison-Wesley, October 1995
-  Continuous Integration - Just Another Buzzword? , by Steve Konieczka, Steve Berczuk and Brad Appleton ; CM Crossroads Newsletter, September 2003 (Vol. 2, No. 9)
-  Codeline Merging and Locking: Continuous Updates and Two-Phased Commits , by Brad Appleton, Steve Konieczka and Steve Berczuk ; CM Crossroads Newsletter, October 2003 (Vol. 2, No. 10)
-  Build Management for the Agile Team , by Steve Berczuk, Steve Konieczka and Brad Appleton ; CM Crossroads Newsletter, November 2003 (Vol. 2, No. 11)
-  Software Configuration Management Patterns: Effective Teamwork, Practical Integration ;by Stephen P. Berczuk and Brad Appleton; Addison-Wesley, November 2002
- Jeff Grigg, from the extremeprogramming mailing list.