-
Notifications
You must be signed in to change notification settings - Fork 5
Approving a test
Luis Bermudez edited this page Jun 25, 2019
·
13 revisions
The processing for approving a test is as follows:
We need 3 early implementations or 1 early implementation and test has been long enough in the beta validation website.
Process (per conformance class):
- 1. Release in beta
- 2. Quality Check
- check that conformance classes match (exact names form the specification)
- confirm the correct version of the specification that the test represents. In particular check for corrigenda versions. Needs to be clarified in the welcome page of the test
- check that there is at list one core test
- if possible check that there is a unit case for each conformance class that test failing
- 3. Get early implementers
- 3.1 Notify the registered implementers
- 3.2 Notify the SWG
- 3.3 Promote in OGC newsletter
- 3.4 Promote in socially media
- 4. Notify CITE SC (2 weeks)
- 5. Notify TC chair for TC approval
- 6. Move to production
- 7. Promote in social media