DRAFT MINUTES
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff: na
Community: Herbert Damker Rafal Artych Jose Luis Urien Pinedo Surajj Jaggernath Patrice Conil Thorsten Lohmar Akos Hunyadi Ramesh Shanmugasundaram Toshi Wakayama Fabrizio Costa , G Vidal, Andrew Wajs Maximilian Laue Eric Murray
Agenda
- Antitrust Policy
- Review of previous meeting minutes
- Agreed
- General Topics
- Patch release v0.10.1
- Further Open Pull Requests
- New Issues
- Release Process and planning for v0.11.0 / v.1.0.0?
- Existing Issues (partially addressed)
- Any Other Topics
Minutes
Patch release v0.10.1
- #277 Fix maximum duration in session info and improve documentation
- Review comment(s) to be addressed
- Explain semantic of "maximum duration" in term section, that always referring to the "remaining" duration.
- Limit will in future defined by the maxDuration of the profile
- If an operator is further restriction, this can be enforced by not granting the extension of a session
- Herbert Damker will update the PR and ask for a final review
- Ready for final review?
- Review comment(s) to be addressed
- #279 Create patch release v0.10.1
- Already "pre-approved"
- Can be merged and release created after #272 is done
Further Open Pull Requests
- PR #273 feat: add the
statusInfo
as parameter to theSessionInfo
- PR to resolve issue #267 within v0.11.0
- Tbe merged after v0.10.1 patch release is done
- Ready for final review.
- PR #275 Upping the checkout action in the swagger validation to remove a warning
- Ready to be merged → Herbert Damker
- Any further issues regarding linting to be opened? → new issue for redoc.
- PR #228 and #217 still in draft mode.
New Issues
- #276 Question on the anyOf in DeviceIpv4Addr
- Request to raise opinions within the issue.
- Patrice will test both solutions with code generator in use
Release planning v0.11.0 / v.1.0.0?
- New sequence towards a "public release" (on our example 0.11.0)
- For "work in progress" current proposals of RM is to use only "wip" in the version number field.
- 0.11.0-alpha.n ... optional releases during development phase
- decision is up to the sub project to create them
- 0.11.0-rc.n ... sequence of release candidates, to be used by implementors
- Public release either
- 0.11.0 or
- 1.0.0, depending on fulfilment of criteria and TSC decision
- Milestones and Release Process -
- see Meta-release Fall24 and CAMARA Release Process (under discussion in Release Management)
- Assumption: scope of Commonalities known at M1 (30.4.), release candidate available at M2 (15.6.), afterwards only bug fixes
- What is the expectation to sub project at M3?
- Feature development mostly done? (an alpha release?)
- Adaptation to latest changes of Commonalities & ICM have to be done afterwards
- What would be a latest date for v0.11.0-rc.1?
- Last (stable) release candidate on M4 (31.08.), all prerequisites/criteria for the "public release" to be fulfilled until then
Existing issues (only the ones discussed):
- #272 Maximum duration 86400 in SessionInfo cannot support 'Extend Session Duration'
- Addressed by PR #277
- #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
- In addition we have to decide about the title, see https://github.com/camaraproject/QualityOnDemand/issues/265#issuecomment-2039406276
- Request for action: please raise your opinions within the issue, it is important to be able to start the work on the PR
Any other topics
- Next QoD will be on April 19th, at 14:00 CEST / 12:00 UTC.
Action items
- Update the PR #277 and ask for a final review until next Wednesday Herbert Damker
- Create patch release by merging #279 after #277 is merged Herbert Damker
- Merge PR #275 Herbert Damker
- All: raise opinion within issue #265 about the title and basepath of the splitted QoD session API