The StreamBrowser and
File Browser enable you to see what individual versions are present -- and perhaps active -- in a stream. AccuRev also makes it easy to answer questions like these:
The key is to go beyond thinking of individual versions to considering collections of versions, called
change packages. With AccuRev, change packages are implemented by AccuWork issue records. An issue record records the details of a bug or feature: its description, how important it is, who originated it, who's working on it, and so on. In the AccuRev Enterprise version of AccuWork, an issue record can also keep track of the changes that have been made to elements, in order to implement that particular bugfix or new feature.
See Patches and Change Packages on page 172 for the precise definition of "between".
As the versions in a change package are promoted up the stream hierarchy, the change package itself implicitly moves up the hierarchy, also. Roughly speaking, a change package has risen to a certain level if all its entries have risen to that level. More precisely:
AccuRev assumes that changes made to an element remain in that element as subsequent versions are created. Suppose a change package entry consists of versions 13/4, 13/5, and 13/6 of some element. Another user then brings version 13/6 into her workspace with an
Update, and creates descendent version 49/2. It's fair to say that the change package entry is "in" her workspace, and in any stream to which version 49/2 is promoted.