Hi,
If we want to directly commit this to trunk without creating a branch,
I first need to thunk about possible consequences when we refactor
exising code.
Stefan maybe has also some ideas about that.
Right, wait for Stefan's and Ede's advice.
It must make use and adoption simple, not more complex !
Michaël
2012/1/10 Benjamin Gudehus <hasteb...@googlemail.com
<mailto:hasteb...@googlemail.com>>
Wouldn't be enough to add a new package to the source trunk for
developpers and to exclude the package for releases, and
nightly builds ?
Michaël
Okay. I will relayout the existing source code to fit into the
structure of
core/trunk.
After that I will create a new branch at svn with the integrated
test environment.
What are the right commands to create this branch in svn? I last
used svn in
2006 or so (I usually use distributed VCS like mercurial and git).
--BEnjamin
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
