As there has been a reoccurring theme on the mailing lists on being more structured in our approach to version control I thought that I would make a recommendation for discussion.
It sounds like we're not ready to change systems (svn->git) so perhaps a middle ground would be to at least follow some best practices in svn and have "branches" and "tags" directories. Assuming that's acceptable to everyone I think the next logical question is, how would that affect our workflow? First we would need to move the current directories to the branches/ folder. Then the next question, how do we manage releases? For the time being I propose this: 1. *-dev is considered stable enough to test -> tag alpha or beta release(s) 2. Once it's considered stable we do two things: 2a. Merge that svn revision into the non *-dev folders. 2b. Tag a release from there (non-alpha/beta). Thanks, Richard KF5OIM
------------------------------------------------------------------------------
_______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
