Having "views" of package sover a DB

[Martin Terreni]

We have a very large repository with the "released" design, but part of the groups need also a working copy.
Lets say development group A is working on a released design in the central DB for iteration 1. Meanwhile design group B is creating the changes on the design for iteration 2. Once group B finishes it needs to overrun the design of iteration 1 with the one for iteration 2.
We were thinking of creating a plug in which will enable users to choose the packages they need to change for the next iteration from the central repository, move them to a working copy repository with all their dependencies and when the iteration is done replace the packages in the central repository with the packages from the working copy repository.
This will enable different design groups to have a working copy of the design and a release copy and be able through automation to update both and overrun one with the other.
Of course don't mean to use merging right now, only one copy counts.
What do you think about developing such a plug in? is it a good way to solve the problem? should we be working else way?