Greetings, We're thinking about adding a branching system to the Asterisk Testsuite. Each branch would be named the same as, and correspond to, an Asterisk branch. So for instance the following branches would probably be created:
13, 14, 15 For each release of Asterisk we will also create a tag in the Testsuite that corresponds to that release's tag. That way someone could checkout both tags for easy testing Other advantages? Most all, if not all, the current versioning stuff found in the Testsuite could go away, or be safely ignored moving forward. The versioning has become a bit cumbersome especially when you have to make a backward incompatible change to a test. Moving the version control out of the Testsuite and into a version control system should alleviate the need for this moving forward. Please let us know your thoughts and considerations on moving forward with this model. Especially any potential pitfalls or problems you might see with it. Thanks! -- Kevin Harwell Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev