Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent...

3
Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, [email protected] Meeting Date: 2013-05-02 Agenda Item: tbd

Transcript of Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent...

Page 1: Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, laurent.laporte@sprint.com Meeting Date:

Report of Methods and Procedures Subcommittee

Group Name: Steering CommitteeSource: Laurent Laporte, Sprint, [email protected] Date: 2013-05-02Agenda Item: tbd

Page 2: Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, laurent.laporte@sprint.com Meeting Date:

Overview of AGREED items

• Advanced discussion on Release Management and AGREED on version numbering schema shown in oneM2M-MP-2013-0131R01:– Details method of managing version numbers for Technical Reports and Technical

Specifications;• Specifies x.y.z schema where: z is for editorial changes; y is for technical changes; and, x is for the

approved version;

– Request that SC APPROVE the version numbering section;

• A modification to the WPD was discussed and AGREED as described in oneM2M-MP-2013-0145:– allows for attendance list of the Technical Plenary to count as attendance in all

working groups;– Voting for technical items and leadership positions would take place during

Technical Plenary;– Request that SC APPROVE the modifications to the WPD.

© 2012 oneM2M Partners<Document number>

2

Page 3: Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, laurent.laporte@sprint.com Meeting Date:

Overview of ongoing items

• Release Management;– Document numbering;– Change control process;

• Work Item numbering schema;• Additional document types for:

– Legal subcommittee;– Marketing subcommittee;– Informative external community;

© 2012 oneM2M Partners<Document number>

3