Change Requests (CRs) for any part of the TTCN-3 Standards are managed by a TTCN-3 maintenance/evolution group which is part of ETSI's MTS technical committee (TC-MTS).
Rules
- TTCN-3 CRs shall only be reported via ETSI's ticket system Tool (gitlab) 'TTCN-3 Change Requests'. (You may read old issues from the past here.)
-
Any CR shall include a FULL solution (example: original text + revision marks) in the attachment.
If the solution is inadequate the reporter will be requested to provide one.
If no solution is forthcoming the CR may be rejected. - The maintenance group may propose alternative solutions. These will be discussed publicly via the ticket system tool with the reporter.
- Any TTCN-3 comunity forum may be used for discussion of CRs and other technical comments but final resolution of all CRs will be the combined responsibility of maintenance group and TC-MTS.
- Wherever possible CRs will be resolved by maintenance group, with the agreement of the reporter. Final arbitration rests with TC-MTS.
Instructions
Anyone can track the status of any CR on any part of the standard with the ticket system tool 'TTCN-3 Change Requests'! Only thing required is to sign up to get a gitlab account or using the ETSI EOL.
Please note that standard maintenance work is not a full-time activity.
You will receive responses within a reasonable time-frame, but probably not immediately.
TTCN-3.ORG site change requests
Change Requests (CRs) for the ttcn-3.etsi.org web site itself are managed by the This email address is being protected from spambots. You need JavaScript enabled to view it.. These CRs can also be reported via ETSI's ticket system tool.
