Branching views and Change Requests

[caz45...@gmail.com]

Hi all,
just wondering if anyone has a nice solution to this problem.
We have a main development branch we are working in, and create sub
branches if needed for specfiic reasons.
If we do one release from the main branch and then go ahead a verify a
lot of CRs in that release, all is fine.
Later, we decide we need to make a small change to that release that
will not pick up other changes being done in the main view, so we
branch off the label.
At the time of the label the CRs were in "fixed" state not "verififed
fixed" so now we have the problem that in the branch the CRs are not
at the correct state.
Those CRs were already verified in the main view so we don't need to
verify them again.

This seems to be a flaw in the use of branches that I can't see a
simple way around.

We can't branch from a later configuration because we don't want to
pick up any other checkins.

This must be an issue other people face, I'm just wondering what
solution you have come up with.