Has anyone tested this structure with Eclipse?  Will it handle multiple
levels of branch directories?  (ie branches/gsoc2007/<student>)  If no one
has tried this, I'll try to test it later tonight.
 
Tom

-----Original Message-----
From: Linus Tolke [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 17, 2007 3:17 PM
To: [email protected]
Subject: [argouml-dev] RE: GSoC students work in the ArgoUML code



I have now prepared and tested this so let me know if you want to use it.

 

            /Linus

 


  _____  


From: Linus Tolke 
Sent: den 4 april 2007 06:52
To: '[email protected]'
Subject: GSoC students work in the ArgoUML code

 

Hello all!

 

Let me suggest the following as a working environment for our upcoming GSoC
students:

*       We create a directory /branches/gsoc2007. 

*       The students get commit access to that directory (this is one of the
benefits of switching from cvs to svn that we will then put to work). 

*       Each student creates the branches that he needs for his work below
/branches/gsoc2007 and commits his work there. 

*       When one piece of work is completed and reviewed, the mentor (or
some other ArgoUML developer) can merge this into /trunk. The student can
use the contents of his branch to deliver to Google and eventually remove
the branch when it is no longer interesting. 

*       The different student projects has different length in their work so
some of these branches will be handled quickly, some will be worked on for
several weeks or months. 

 

I think this is a good compromise of features in development environment,
convenience in merging, and Tigris infrastructure. Of course, there is no
need to use this. If the student or mentor prefers some other way of
communicating code changes for review and merging, then that is still
available.

 

            /Linus

 

************************************************

Linus Tolke

[EMAIL PROTECTED]   [EMAIL PROTECTED]   [EMAIL PROTECTED]

ArgoUML <http://argouml.tigris.org/> 

************************************************

 

Reply via email to