Navigation
News
Buildap 0.7 is now available
Mon, 13 Feb 2006 07:36:54 GMT
SVG Editor 1.0 for Eclipse IDE
Sat, 21 Jan 2006 11:07:12 GMT
Buildap 0.4.0
Fri, 23 Sep 2005 07:43:25 GMT
buildap 0.2.6
Sat, 20 Nov 2004 18:56:40 GMT
Buildap 0.2.4 is available
Fri, 22 Oct 2004 05:30:41 GMT
Graph Editor 0.7
Sat, 06 Mar 2004 07:47:05 GMT
GraphEditor 0.6 is available
Wed, 29 Oct 2003 23:10:14 GMT
SVG Plugin for NetBeans realised
Wed, 03 Sep 2003 14:04:11 GMT
 

 light CVS beta, sandbox, and production

Document Actions
Replies: 1   Views: 4251
Up one level
You need to be a registered member to post to this forum. Register now.
Prev topic | Next topic

light CVS beta, sandbox, and production

Posted by edwardotis at 2004-10-07 04:11
I propose that the CVS repository be split into at least 3 sections.

Production - Only Release quality code goes here. Only an Administrator can commit to the Production branch. Typically a successfully tested Beta codebase is moved all at once to Production.

Beta - PreProduction environment of code that is being tested for next stable release. Developers would submit code to be added to this branch, and the code will be approved or rejected by an administrator.

Sandbox(s) - "In Development" quality code goes here. Developers can commit and add files.

There could be multiple Sandboxes to keep developers from messing up each other's code.

--
I haven't used CVS too much, but this is a general concept I've used in other companies for developing web applications. I'm sure this plan needs revising, so please comment. :)
Anonymous
Posts: n/a

 • Re: CVS beta, sandbox, and production

Posted by amehrabyan at 2004-10-13 13:15
we are going to have at lease 2 section, like 'Production' and 'PreProduction' as you mentioned.

as for sandbox(s) increasing number of sandboxes also can create mess, we try to divide projects in subprojects which can evolve (condiderabely) separate and have its own 'Production' and 'PreProduction' in cvs.
Manager
Posts: 2