Conference smurf::buildhelp

1626.0. "Project Sandbox config. question" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Jul 20 1995 22:32

Date Of Receipt: 	20-JUL-1995 21:28:06.49
From: 	SMURF::WASTED::"[email protected]" "21-Jul-1995 1125"
To: 	[email protected]
CC: 	
Subj: 	Project Sandbox config. question

Hi !

James Overman suggested that you folks may be able to help me with a question about 
project sandbox, submit trees etc when using DECode II (V3.0 - but I think the prinicples
would apply to pretty much any version).

A little background first - we've been using ODE for about 4-5 months on a small 3-4
person project quite happily but as things progress and get larger etc. we're facing some 
interesting code/functionality integration problems.


I have a feeling that the following sort of arrangement of sandboxes, shared sandboxes and
static backing trees should allow us to get over the hurdles of testing the integration before
submitting it for a new baselevel creation.  Our project is fairly self-contained we don't
have any other subprojects or orthogonal projects etc. etc.

Hopefully an arrangement such as below would allow us to test the integration from
two or three developers, incorporate the bugfixes from a previous baselevel into the next
and then create a 'known (pretty) good' static baselevel. Do you think you could confirm my
opinions or set me straight in a few places if I'm adrift ?


			proj.bl_(x)
			    |
			    |
			proj.bl_(x+1)
		      /		      \
	proj.bl(x)_shbf			proj.shsb
	    |				    |
	    |				    |
	developers bugfix			developers new functionality
	sandbox				sandbox.


The proj.shsb shared sandbox should allow integration of new functionality without breaking
any other developers bugfix work etc.

The proj.bl(x)_shbf shared sandbox should do likewise for bug fixes that need to be 
incorporated into the next baselevel. (we dont need to worry to much about tweeking old
baselevels at the moment - since we don't have any real released kits etc. yet)

Then I have a bit of a problem - I feel that we would need a second (shared) sandbox within
which to integrate the new functionality with bugfixes before submitting to the end submit 
tree from which a new static baselevel would be created. ie . at some point in time the 
contents of the proj.bl(x+1) sandbox could be considered good enough for kitting or release etc.
Would this sandbox be a shared sandbox ? or would it be some form of overlapping project ?

Many thanks for any help or suggestions you could give me. I've tried to have a little look 
at how OSF/1 is arranged with pools, submit trees etc., but to be honest the size of it all is a
little overwhelming 8-)

Regards,

Andrew Kimpton,
CSS Engineering,
Sydney.