How (or can) I create the "stream-like" metaphor using SVN?

Hi,

In AccuRev, we created a hierarchy of streams based on the organization and products at the top and then based on the projects and teams at the bottom.

This allowed us to segment the code on a flexible but structured basis. As code changes flowed up the hierarchy, they became more and more integrated into the rest of the organization. Integration testing, for example, was done on key boundaries (or streams) in the hierarchy, ensuring quality at many intervals in the life of a change.

How can I get this stream-like metaphor, either conceptually or in practice using SVN? Keep in mind one goal is to be able to commit a story's work independently of the other stories.

Some background

We currently develop using scrum/agile. So we have sprints and stories. We are branching on each story so that we can commit (or not) each story independent of the other.

The overhead turns out to be more than we anticipated. So we are debating branching on the sprint instead.

SVN supports copy-modify-merge model, which we use.

I am having trouble figuring out how we can create a hierarchy of branches in SVN to do what I was doing in my old company.

It seems I am missing how a branch is like a stream (or not) as mentioned in this post " SVN, AccuRev and BitKeeper (was Re: branching several times a day)".

Is there a way to achieve this idea that code moves up a hierarchy toward wider and wider integration with other teams, projects, and products?

Any insight would be greatly appreciated.

Thanks,

Doug