ats code development workflow group name: tst wg source: mahdi ben alaya, tst wg vice chair,...

ATS code development workflow

Group Name: TST WGSource: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, [email protected]

Miguel Angel Reina Ortega, ETSI CTI, [email protected] Meeting Date: TST #21Document ID: TST-2016-0026-ATS_code_development_workflow

mailto:[email protected]

mailto:[email protected]

Outline• Code repository• User roles and permissions• Code review process• Issues tracking• Continuous integration• Release process

© 2014 oneM2M Partners<TST-2016-0026-ATS_code_development_workflow>

2

Code repository• Which version control system for the TTCN-3

repository ? (Git/SVN)GitLab (github-like, can be hosted locally, provides same functionality but more intuitive, easier, user friendly)

• Where the version control system will be hosted and who will maintain it ? (Users management, Maintenance, Backups, etc.)ETSI (since it is in charge of hosting oneM2M IT)


3

User roles and permissions• Which authentication server ? (oneM2M, ETSI EOL,

Local)Local (at least at the beginning, more flexible)Do we need to fix roles for users ? – Reporters: Report bugs (everyone)– Developers: Send contributions (small group of people from

TST WG at the start, add more people on demand)– Masters: Validate contributions (rapporteur)… ?

• Public or Private access to the TTCN-3 code ?Public

© 2014 oneM2M Partners<TST-2016-0026-ATS_code_development_workflow>4

Code review process• Do we need a code review process ? Yes, 2)• 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.

Validation means checking that TS-0015 rules on writing TTCN-3 are followed (naming convention, quality, etc..) to have consistent code

• How to discuss contributions ? (comments, mailing list, etc.)Through GitLab comment function


5

Issues tracking• Do we need to track bugs in TTCN-3 code ? If yes which tool

(Bugzilla, mantis, etc.)Yes, included in GitLab

• Who can report bugs ? (all or restricted to authenticated members)Everyone

• Who will fix them ? (No rules, or user assignment, etc.)Small developers group (see slide 4)• Important to link bug fixes to their corresponding issues

(traceability).• Gitlab provides that


6

Continuous integration• Do we need to compile dynamically the source

code and each contribution (simplify code review and validation process)Yes

• Which TTCN-3 compiler to set up internally for continuous integration (Titan, etc.)Several should be used (Ttworkbench, Titan, etc..)

• Any additional feature ?


7

Release process• As TTCN-3 code is part of TS-0019, it will be

released at the same time as a TS-0019 baselines, i.e.:

– TS-0019 vX.Y.Z– TTCN-3 code tagged in GitLab vX.Y.Z.


8

ats code development workflow group name: tst wg source: mahdi ben alaya, tst wg vice chair,...

Documents