I had a crazy idea in a dream last night. Am I way off base? Is there a
better way?
Problem: I need to store information about each 'task' branch. Something
like release notes for each task. It contains Task information, Coding
quality information, Server performance information...
Idea: Has anybody out there created 'Branch Release Note' which Logs branch
specific information (in a format which can later be imported into a DB).
The way I see it working is
a) Create a special compress_file element, BRANCH.LOG in the
VOB:main
b) When a new view is created, BRANCH.LOG is checked out
c) BRANCH.LOG is cleared if its header infomation doesn't match this
branch.
d) Text data is logged as needed to BRANCH.LOG
e) BRANCH.LOG is copied over because of the element type during
delivery
f) The version history of BRANCH.LOG in the integration branch shows
the delivery history of each of the tasks!
History: Vobs branch, 'main'(core code) to 'product' branches to
'integration' branches (development & maintainance) to 'task' branches. CC
3.2.1 patch 15.
Solution tried:
1) Integrate with ClearQuest to track all of this information
a) My company is tied into another less flexible defect tracking DB
(PVCS Tracker).
b) $$$ Cost of ClearQuest is a barrier
c) seperate application ties branch information to branch
2) Store everything as an attribute of the task branch.
a) Slow
b) Some text attributes are too long, i.e. 'Test Performed:' can be
pages
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:31 EDT