...
...
...
...
...
...
...
...
...
DRAFT MINUTES
Attendees & Representation
...
- Meta-release Fall-24 - timeplan updated
- https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/x/cgB0AQFwDe
- Expected Deliverables
- M0 - approved, but communication delayed (expected begin of next week)
- M1 - 30/04
- Scope of Commonalities finalised:
- Scope of ICM in work, focus on OIDC profile
- The release process definition expects here already an alpha release of Comm & ICM, but they will come only later, at latest 2 weeks before the release candidates (for review by API Sub Projects)
- M2 - 15/06
- (Release candidate of Commonalities + ICM)
- M3 - 15/06
- First release candidate of QoD, starting of test implementations
- Won't fit if there are last minutes changes from Commonalities + ICM
- Instead an v0.11.0-alpha.1 release as milestone target?
- First release candidate of QoD, starting of test implementations
- M4 - 31/08
- Last (stable) release candidate of target release from QoD
- Release Criteria fulfilled (incl validation of the release candidate by two independent implementation of the API)
- M5 - 15/09
- public release done
- PRs #273 and #283 merged
- License file added to the repository (copy from template repository)
- EasyCLA deactivated on the repository (until a final decision about EasyCLA vs DCO, see TSC Minutes)
- New GitHub teams @camaraproject/quality-on-demand_maintainers and @camaraproject/quality-on-demand_codeowners - please accept the invitation to the camaraproject organization.
...
- PR #289 Split QoD in Quality-On-Demand and QoS Profiles APIs
- New PR, addressing issue #265 – need to merged before other PRs can be created
- Naming will be accepted as proposed for this PR ... can be discussed separately and changed if needed
- One week of review ... will be merged on next Friday if no open comments.
- PR #228 and #217 still in draft mode.
Closed issues
- #282 Move example outside of allOf in schemas.Duration
- Fixed with PR #283
- #276 Question on the anyOf in DeviceIpv4Addr
- won't fix
...
- #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
- Jose Luis Urien Pinedo to make first proposals
- discussed about maxDuration → establish again as absolute maximum
- discussed about default for duration
- making duration parameter mandatory could be an option
- #290 Current CI expects certain fixed name for yaml spec
- Drop the GitHub action for now, bring only back if we encounter anomalies which are not catched by MegaLinter
- #288 Duration behavior during session extension
- see #291
- #286 Review Attribute Descriptions with References to External Specifc
- Herbert Damker check where QoD would be impacted
- Maybe into backlog until implementation experiences are available
...