Page Comparison

...

...

Thorsten repeated that the Anti-trust policy applies to this meeting and that the policy can be found in the notes.
Thorsten understood in the all hands meeting that we should not target the Spring release
- since the Dedicated networks api is a sandbox api
- should use the label “camara others” (or similar)
- how would sandbox api show up in meta release
- Jorge: sandbox group cannot release a 1.0 - first need to do an initial release - test with operators - then can be moved to stable release work flow
- Thorsten updated text in scope to reflect this

M4 milestone (Feb 2025 end) implies that API should be almost ready for the meta-release
M3 - thats the first deadline to start working against

Thorsten: Scope issue
- Bit awkward to start documenting as issue
- Should ideally move to release documentation at some point
- Should also include what is NOT in scope
- WoW: Update scope issue in the meeting but also possible to make comments which can be reviewed and updated during the meeting
- Thorsten checked the APIs - some point to open issues. For Dedicated Netowrks - should start with initial requirements. Can point to more issues later
  - Phrase in the form of requirements
- Current thinking is to start looking at the API description
  - Take hints of the requirements from above and convert to “real requirements”
  - Scope should cover at least what is written above
- Jorge: For the release, user stories are required
  - In development pipeline, this is a typical workflow to start with user stories (even though other APIs did this in the end)
  - Could we start with user stories now?
  - Thorsten updated the comment directly in the scope issue.
Jorge gave example of Device swap etc. on how a sandbox API could be part of meta-release
Thorsten: What about the testing material
- Jorge: API test plan - at least the happy paths - need to be documented (simple test plan)
Thorsten: Need to start working on the first draft of first user story

Action items