-
Notifications
You must be signed in to change notification settings - Fork 9
Standup summary: 2025‐07‐24
Sam Clarke-Green edited this page Jul 24, 2025
·
1 revision
- PR #435 has been committed and other issues have been unblocked.
- PRs have been opened for command line tool changes.
- We have switched to a fortnightly schedule for standup meetings
- Kanban board has been updated
The following points of discussion came up in the meeting:
@hiker has sent an email containing supporting reasons why site specific files are required. The feature is already present in baf, but it is not clear how the files should be managed. The important concerns were:
- Sites should be able to manage their own configuration files
- Sites cannot test each others' configurations
- It should be possible to self-review site-specific information without requiring a Met Office reviewer
- Site files should be publicly visible
- Configurations can provide new sites with useful initial starting points
- Files should be kept in the same repository as the application code
There was a discussion of the plan to create git repositories with stable and main branches. It was expected that the initial use of git would be similar to fcm, with users branching from a release tag on the stable branch.
- Cancel monthly meetings (carried over)
- Finish curating the issues list (carried over)
- Check reviews for release PRs are in progress
- Present suggestions about site-specific configurations at NGMS meeting
- Future Release
- vn1.0 Release, March 2023
- 0.11 Beta Release, Jan 2023
- 0.10 Beta Release, Oct 2022
- 0.9 Alpha Release, June 2022
- 2.0, July 2025
- 2.1, August 2025
- Phase 2
- Phase 3
- Phase 4
- Repository Management
- Development Process
- Development Environment
- Releasing Fab
- Coding Conventions
- Glossary
- Concerning the Database
- Unit Test Coverage
- Issues With the System Testing Framework