Hi all,

About the Scilab-6 project, we do not need any new branch because we already have one (gsoc2009-sploving) which has never been merged into the trunk and contains the whole Scilab-Swig wrapping code.


Le 28/04/12 14:14, Vadim Zeitlin a écrit :

 Should we create svn branches for the students already? Unless we plan to
switch to git some time soon (wink wink nudge nudge :-), I think we should
do it a.s.a.p. to let people start working even before the official GSoC
beginning if they feel like it, any objections? If not, should I just
create the branch for the student whom I'm mentoring or will William create
all branches at once? And, if I do need to create it myself, should we
branch from rel-2.0.5 or the current trunk?

 I'd also like to use slightly different branches names if possible: the
current convention is to use gsoc$YEAR-$STUDENT (see
http://swig.svn.sourceforge.net/viewvc/swig/branches/) but this is not
terribly clear for someone not intimately familiar with the project so what
about using gsoc$YEAR-$PROJECT-$STUDENT or, perhaps, just gsoc$YEAR-$PROJECT
as presumably the students know which project they're working on anyhow?
E.g. something like gsoc2012-c-backend[-leif.middelschulte] for the Leif's
project that I'd be mentoring?


Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Swig-devel mailing list

Software Development Manager
Consortium Scilab
Domaine de Voluceau
Rocquencourt - B.P. 105 
78153 Le Chesnay Cedex France
Tél. : +