Page Comparison

DRAFT AGENDA

...

...

• Migration of wiki.camaraproject.org into Atlassian Cloud
  • Was tentatively scheduled for August 29th ...was delayed due to an issue with linking to meeting templates.
  • New deployment date will start on 23 Sep 2024 
    • migration delay was due to broken links in template mechanism in the "create minutes" button on landing page. From now on: use the "create new minutes page" button on the parent page of the minutes list
    • friday outage was due to license expiry as the migration was supposed to have happened already - Atlassion Atlassian is deprication depricating their data center solutions.
    • A note about the new Cloud deployment.  Other communities have experienced issues with "copying" previous minutes' pages.  It is suggested to always use the create from template button, which will be moved to the "2024 <project/wg> Minutes" parent page.

...

• Meta-release Fall24 - CAMARA Project - Confluence
  • M5 declared, as announced on the all mailing list (https://lists.camaraproject.org/g/all/topic/camara_fall24_meta_release/108462715)
• Next release cycle ("Spring25") starts on September 30th (M0 - Kickoff)
  • Initial indication that the M1 may need to be delayed. Date to be determined next week in RM meeting.
•  M6: feedback on release process welcome from all participants. Please provide feedback either as a GitHub issue in the ReleaseManagement repo or on the Meta-release feedback page.
  • Updates to the process will be incorporated for use in the upcoming meta-release.
• Request from Jorge Garcia Hospital to check if we can align the release of the Meta release with the MWC (3-6 March 2025)
  • This was on purpose to avoid confusion between Telco API announcement release vs meta release announcement
    • This is probably a point to be discussed with GSMA communication/marketing team
• Eric Murray raised the question about breaking/non breaking change assessment - up to the RM team or by Project?
  • Tanja de Groot answered that we have a section "guideline" on this topic here
  • The information are also in the Commonalities documentation in the Section 5 on versioning
  • Maybe be we can check if linting rules could help for this (to be check with Rafal Artych )
    • Jose Luis Urien Pinedo has doubt about linting help on this as linting prevent merging. 

...

• An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for 30 Sep 2024
  • Since 5 APIs are now stable - how to deal with guidelines enforcing breaking changes in API specifications?
  • Herbert: add in the PR template a section on breaking changes and that indicates that there is an impact on API - the PR description should be updated accordingly.
• M1 date for Spring25
  • Current date too early for the first alpha release
• Eric: versioning numbers - review the versioning number → raise of Commonalities and ICM → Eric to raise an issue in commonalities/ICM
• Herbert: There is a proposal in RM to use the release numbering for overall release, not the version number: Align also Working Group release numbering with the rx.n numbering schema starting in Spring25 cycle · Issue #94

Identity & Consent Management  (Axel Nennker )

• ICM patch release r0.2.1 Waiting for approval by release-management - fixing broken links
  
• Discussion on signed authentication requests #194
  • clarify what must be signed and by whom ? can it be rejected ? details in issue #194 (see link above - please comment
• Sorting issues into what is planned to be included in Spring25
  • team is asked to create PRs with specific change proposals.

Specific Topic: Arazzo Specification discussion (Kevin Smith )

• moved to next meeting

Any Other Business

• Eric: we should be organizing new TSC elections - Casey will organize and discuss details. 

...