-
Notifications
You must be signed in to change notification settings - Fork 3
Release Debrief for v1.0.5
Joost van Ulden edited this page Nov 22, 2022
·
1 revision
November 22, 2022 Meeting Outcomes
- Bo L.
- Sebastien D.
- Eleni L.
- Chris M.
- Pascal V.
- Sean E.
- Johann L.
- Joost v.
- Review process not clear. The content review was not formally carried out in Staging and approvals were not specifically provided for all changes
- Testing can be improved. Testing is carried out by several people with internalized knowledge of what to test. No formal integrated test script exists but people have checklists that are followed for every release
- There are planned CI/CD optimizations that have not yet been implemented due to a lack of resources - consequently there are some manual processes required that are error-prone and can introduce a regression
- Release window was not clearly defined in advance
- Some people were not fully aware of what was deployed in DEV vs. STAGING
- UI translation is sometimes carried out using third-party tools rather than NRCan officials
- Release process documentation needs to be consolidated and made available more widely
- CI/CD optimizations need to be implemented
- Testing needs to be expanded to include API endpoints and Geocore
- Front-end testing needs to be automated (e.g., Selenium)
- Test script(s)/process(s) need to be documented
- Release process documentation by March 31st, 2022 (Joost to Lead)
- GeoCore conformance test by March 31st, 2022 (Chris/Bo)
- Look into Selenium for testing UI (???)
- Implement GitHub actions for automating the configuration of static content (Chris/Bo/Pascal)