[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Queries regarding SVN

From: Michael Jacob <michaeljacob_at_tataelxsi.co.in>
Date: Wed, 09 Mar 2011 17:23:13 +0530
Dear Concerned authority.

Please find below mentioned issues. Please do respond to these issue's solution at the earliest. Thanks in advance.
  • Insufficient evidence on review activity from the CM tool: The current configuration Management tool SVN looks in sufficient to fulfill on all aspects of configuration managements. Consider the scenario of a file of revision 1.0 got updated to 2.0 due to the review record xxx_file_reviewrecord. Currently there is no evidence/proof that revision 1.0 got updated to 2.0 is due to the review activity and because of the review record xxx_file_reviewrecord. The suggestions we are giving as part of committing  a new revision is not enough to substantiate that review has been performed over revision 1.0. There should be a sort of relation mechanism in a configuration management tool(like PVCS do) to evident the changes in the revisions.
Please provide the solution if my understanding is correct.
  • Regarding Base lining for a release: Baselining is meant to label together all the Inputs(Documents,Source Code etc.) and Outputs(CTE's, Tessy Reports etc) which have been used for that particular Release. Consider the below scenario. Suppose the input document(SRS) is present under path ../trunk/Static/SRS on which we have worked and resulting output document is placed at ../trunk/Controlled/CTE. In ideal situation we should be able baseline these two versioned files with a baseline tag from the mentioned different paths.It means that we have taken the correct input from the correct path.
          But in SVN, we have to take out the SRS from ../trunk/Static/SRS and CTE from ../trunk/Controlled/CTE and has to place in a single folder to Tag/Baseline            it. We will be delivering this function to end customer. Hence it means that there is no evidence that the files under new Tag folder is correct and same as                actual files. It doesn't substantiate that we have taken the correct input from the correct path on performing the CTE development activity.

Please provide the solution if my understanding is correct.
  • There should be a Traceability report over Configuration Management baselines to trace the deliverables belongs to which Baseline label and which inputs.
Please provide the response.

Michael Jacob

Received on 2011-03-09 13:03:06 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.