Repository Workflow Guidance
This generic workflow is designed for supporting amendments and applies to the following repositories: BUFR4, CCT, CF-NetCDF, GRIB2, and WMDS.
- Stakeholder: This may be an expert who registers the issue, helps validate or in general has a vested interest in the outcome.
- Team and Facilitator: Prioritises the issues, develops solutions, validates the results and verifies the amendment report.
- Team Chair: Leads the team, assigns facilitators and notifies the Secretariat.
- Secretariat: Creates branches, develops the amendment report and merges branches into master after amendments are adopted.
- Submitted: An issue is registered and added to the project. The team determines if the issue should be worked on. If no, then add an explanation and close the issue. If yes, the chair assigns team member to facilitate the issue and move to "In Progress". The facilitator "owns" the issue, engages stakeholders as needed and maintains the issue until it is closed by the Secretariat.
- In Progress: Facilitator and team propose a solution, document it clearly in GitHub and engages stakeholders/domain experts as needed. When there is consensus, the Chair moves the issue to "In Validation" and notifies the Secretariat.
- In Validation: The secretariat creates a branch from Master. The facilitator updates the branch based on the determined solution and another designated individual validates the branch using sample data. When it's valid, the chair moves issue to "Validated" and notifies secretariat.
- Validated: The secretariat verifies that the issue is well documented, merges the issue branch into a fast-track branch, deletes the issue branch and prepares a consolidated proposal for amendments in a document. The consolidated branch should be named "FTYYYY-#", e.g. "FT2023-2".
- For Approval: The issues are closed unless feedback requires more work on the proposal. The proposal for amendments is submitted for approval through the fast-track procedure. The Secretariat merges the FT branch into Master branch and tags a release candidate. One issue is opened to keep track of the status of all proposals during the fast-track procedure.
- Fast-track procedure: approval by Chair of SC-IMT, NFP review, approval by P/INFCOM and then approval by P/WMO.
- Publication: After approval by the P/WMO, the Secretariat tags a release, publishes codes to the web and http://codes.wmo.int as needed and sends the amendments to LSP for translation and publication in the Manuals.