From bricks to walls...

After dealing with the stream concept a lot of doubts immediately showed up...

1. How real files in my computer become elements of a stream?
   Here Accurev created the concept of Workspace that is really a special stream that has an association with a folder where the files we want to put under versioning control reside.
2. That means I have to put all my files on the same directory for versioning control?
   No no, we can create many Workspaces, let say a Workspace per project in every member's team PC.
   
3. Where are the elements really stored?
   The Depot. The Depot is an Accurev proprietary database where all the files and its different versions plus the versioning control meta data are kept. When we install Accurev we define a physical location for this database.
4. Well, then the streams do not keep the files on them?
   Not really, streams are not file directories. They are just an element of a map that represent our software development process...
5. How can I build that map with streams?
   Big question, at this point I've got stucked with Accurev documentation...
   The thing is to represent with streams the flow of our software development process... let say for Project X we might have an Integration stream where several programmers are putting together a first version. When the project is ready for testing we might want to do this in a Testing stream. After testing we release using a different stream, and finally we maintain in a maintenance stream... Yes I know, it sounds so simple but...
6. Probably is time to know how the flow among those streams is...
   It comes next entry.