2011-06-14 03:15 AEST by Glen Starrett - A customer describes their process through the promotion levels as containing
10-20 bugs.  It would be useful and less error-prone if they could associate the
10-20 bugs to a single "parent" or "release" bug ID, that CVS Suite Server then
expanded out to the 10-20 bug count by querying the bug database.

For example:
-- Development works 20 bugs associated with RELEASE 2.
-- Dev manager creates RELEASE 2 bug and associates all 20 individual bugs as
subordinate bugs in the bug system (e.g. the 20 bugs each "block" the RELEASE 2
bug in Bugzilla).
-- Release manager promotes release 2 from the development HEAD to TEST
promotion level using the single bug id for RELEASE 2.
-- CVS Suite Server gets the RELEASE 2 bug and queries the 20 bugs, then
processes normally.

Notes:  This isn't Tortoise-CVS friendly, might not work as expected as written
here by TortoiseCVS users because they won't get to see a list of files affected
prior to the merge operation, but I don't think they get that anyway.  They will
get to review before the commit operation is done.

For the commit operation, the files should have metadata of their original bugs
(and maybe the RELEASE 2 bug as well??) so all will be tracked against the
original bug ID's.

Might need some added nomenclature (e.g. "-b 321+" where the + triggers the
search/expansion routine) to the triggering bug so it doesn't unintentionally
grab bugs that are marked as subordinate in other methodologies, or a control
panel enable switch.