We definitely need to discuss this first but I think we have enough people
touching the code that we need to start using "branches" in svn. Well
technically in svn, from what I understand, it's all just directories, but
in a typical project there would be a "branches" directory and "tags" or
"releases" directory off the main project branch.
These would be used for situations like this so development could continue
outside of the main or "devel" branch not pollute it.
Long term we may want to look at git, where tags and branches are real
things, not just directory structure, but I know everyone is comfortable
with svn right now.
Thoughts?
Richard
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
