TF001 Progress report Group Name TST WG Source

Outline • • TF-001 Progress Report Development process ATS Status Other issues © 2016

TF-001 Progress Report • Conf call on 8 th September • • • Naum

Development process Member A Group X TF-001 Git. Lab Branch X Member B Group

ATS Status • Contributions from: – ETSI for DEL and SUB groups – Fraunhofer

AOB • Two mailing lists have been created: – onem 2 m_tf 001_developers for

Thank you for your attention © 2016 one. M 2 M Partners <TST-2016 -0122

Slides: 7

Download presentation

TF-001 Progress report Group Name: TST WG Source: Miguel Angel Reina Ortega, ETSI CTI, miguelangel. reinaortega@etsi. org On behalf of TF-001 Meeting Date: TST #25 Document ID: TST-2016 -0179 -TF-001_Progress_Report

TF-001 Progress Report • Conf call on 8 th September • • • Naum Spaseski (EGM) Ting Martin Miao (KETI) Axel Rennoch (Fraunhofer Fokus) Bogdan Stanca-Kaposta (Spirent) NEW Gyorgy Rethy (Ericsson) NEW – Distribution of tasks – Working procedure and plan • Mainly emails to synchronize among team members © 2016 one. M 2 M Partners <TST-2016 -0122 -TS-0019_ATS_Progress_Report> 3

Development process Member A Group X TF-001 Git. Lab Branch X Member B Group Y Git. Lab Branch Y Member C Group Z Git. Lab Branch Z Adjustments needed Git. Lab Merge and checking of free errors compilation TF-001 Team leader review TS-0019 Contribution (Git. Lab tag) TS-0018 CR contribution All OK TF-001 Activity report © 2016 one. M 2 M Partners <TST-2016 -0122 -TS-0019_ATS_Progress_Report> 4

ATS Status • Contributions from: – ETSI for DEL and SUB groups – Fraunhofer for GMG group – KETI for LOC group CRE DMR UPD RET 24 43 DEL 48 GMG 25 42 LOC 21 DIS 13 SUB 0 SEC 21 REG 0 Total 5 242 Total without permutations 89 © 2016 one. M 2 M Partners <TST-2016 -0122 -TS-0019_ATS_Progress_Report> 5

AOB • Two mailing lists have been created: – onem 2 m_tf 001_developers for TF members (for technical discussions) – onem 2 m_tf 001 for anyone to ask questions or get info about TF • Git. Lab Issues tracker and emails mainly used to sync up among TF members • Still need to define a process for handling, collecting and contributing the required changes in TS-0018 among the TF 001 members • Due to lack of TPs, TF members were asked to write new TPs (on behalf of their company) to be able to implement them on TTCN-3 (on behalf of TF-001) Again, TST WG needs to feed TPs to TF-001!! © 2016 one. M 2 M Partners <TST-2016 -0122 -TS-0019_ATS_Progress_Report> 6