Is this NT or Unix ?
-----Original Message-----
From: Julie Rudinski [mailto:julier@techapp.com
Sent: Wednesday, February 23, 2000 2:19 PM
To: cciug@Rational.Com
Subject: [cciug] Build Procedures/Policy
Hello everyone,
I was wondering if I could get some input on how everyone manages their
build schedules.
Currently we have a development branch which all the work is done on. The
developers check in their code when they are finished and when it comes time
to build I pick up the latest elements on the development branch. This has
caused a few problems with files not being checked in, and developers not
testing their code.
I want to enforce a more "strict" policy. My idea is as follows:
All changes to the code are related to a software change number and I
have a script prompting for the SCR# upon check in. An attribute is then
placed on the element. <This is the new part --> I want the developers to
submit the SCR# with a listing of all changed files (I have a script for
this, they just need to run it). Then I can build based only on the
submitted SCR#'s.
Unfortunately, the developers are adamantly against this idea because it
requires them to do extra work (running a script) and remembering to submit
their SCR's. (since I said non submitted SCRs would not go into the build).
So I am back to square one, building the latest elements which I do not
think is adequate procedure.
Does anybody have any suggestions?
I would appreciate it greatly.
Thank you,
Julie Rudinski
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:31 EDT