1. ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, benalaya@sensinov.com Meeting Date: TST #21 Document ID: TST-2016-0026-ATS_code_development_workflow

2. Outline Code repository User roles and permissions Code review process Issues tracking Continuous integration © 2014 oneM2M Partners 2

3. Code repository Which version control system for the TTCN-3 repository ? (Git/SVN) Where the version control system will be hosted and who will maintain it ? (Users management, Maintenance, Backups, etc.) © 2014 oneM2M Partners 3

4. User roles and permissions Which authentication server ? (oneM2M, ETSI EOL, Local) Do we need to fix roles for users ? Example: – Reporters: Report bugs – Developers: Send contributions – Masters: Validate contributions – … ? Public or Private access to the TTCN-3 code ? © 2014 oneM2M Partners 4

5. Code review process Do we need a code review process ? Two possibilities: 1.developers push their contribution directly to the master branch. (Code review done separately at the end, difficult to manage) 2.Developers contribute via “pull request” mechanism. Each contribution is validated before merging. How to discuss contributions ? (comments, mailing list, etc.) © 2014 oneM2M Partners 5

6. Issues tracking Do we need to track bugs in TTCN-3 code ? If yes which tool (Bugzilla, mantis, etc.) Who can report bugs ? (all or restricted to authenticated members) Who will fix them ? (No rules, or user assignment, etc.) Important to link bug fixes to their corresponding issues (traceability). © 2014 oneM2M Partners 6

7. Continuous integration Do we need to compile dynamically the source code and each contribution (simplify code review and validation process) Which TTCN-3 compiler to set up internally for continuous integration (Titan, etc.) Any additional feature ? © 2014 oneM2M Partners 7

8. Thank you for your attention © 2014 oneM2M Partners 8