Like alot of people, I haven't looked at the code in several months, much
less touched it. But I certainly agree that ADC needs some work.
However - the basic ADC.<ArchitectureName>.<Feature> translating to
ADC.<Feature> is one thing that cannot be changed easily. Segmentation
within the confines of that schema should be okay though.
As far as branching/tagging, and then re-merging - it is fairly quick and
easy. If you are using TortoiseSVN on Windows, take a peek at the manual -
its rather straight-forward.
So uh, have at it, as far as I'm concerned. What really counts though, like
you said, is the opinions of those that are actively working in branches.
And depending on the status of such individuals in those projects, you guys
may want to meet together and go ahead and get some of the dangling projects
merged into trunk. Just make sure you don't break trunk functionality that
already exists, and that any newly merged code is clean and sane and
compiles, whether its finished or not. (And then go back out to branches
*again* to finish up.) That way you can all work from a common reference
point.
Its good to see you guys keeping the dream alive. The rest of us have gotten
lost in the real world...
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
