Re: Merge to trunk
"Christian Van Brussel" <[email protected]>
| Newsgroups | gmane.comp.graphics.crystalspace.devel |
|---|---|
| Message-ID | <[email protected]> |
> How would this split affect shared resources like the iModifiable > interfaces that probably > have to go to CS instead? > > Otherwise I'm fine with this split. Just a bit worried about such a branch > getting outdated as > it has happened in the past. But if this branch contains ALL the tools > (viewmesh, lighter2, ...) > then I guess it is not as likely. Yes, some parts of the 'editor' branch would be merged in trunk, that is the iModifiable and its related classes/apps. Those are however not yet completely ready, therefore this merge can probably wait a bit, and the iModifiable may not be a target for CS 2.1. The remaining work that is in the 'editor' branch, namely the cseditor and the new libcrystalspace_gui library, would be moved directly from the branch into the new CSTools library. After that the 'editor' branch would not be used anymore. The other preprocessing tools that are currently in trunk (lighter2 etc) would be moved by small steps from the CS trunk to the CSTools, therefore they shouldn't get outdated. ------------------------------------------------------------------------------ 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/