Page Comparison

Policy framework began the review of 5yr questionnaire and will complete the review at the 22 August meeting.

Adheli Tavares will attend 2023/09/05 meeting to complete review.

Update from 2023-08-21 PTL meeting

-CPS (Toine Siebelink): will test building CPS without oparent/pom.xml (results 2023-10-01)

-Integration (Marek Szwałkiewicz): will perform a test build with the profiles commented out

2023-08-15 SECCOM notes

-Only 2 PTLs responded to Amy’s e-mail

-No objections on Oparent retirement, we have no volunteer to maintain it up to date

-pom.xml contains more than cross project common package dependencies

Oparent is more than just standarizing packages.

Recommendation:

-retain oparent/pom.xml

-Make Andreas Geissler a committer and ask the integration or OOM team to update the file per release

-Proposal:

• Option 1 (short term): ask the integration or OOM team to update the file per release
• Option 2 (long term): split into multiple pieces that could be independently maintained: dependencies, build directives, profiles

-Byung will discuss with Andreas and OOM team and report at 8/22 SECCOM (pushed to 8/29 SECCOM meeting)

-Amy will contact Liam Fallon  and Pam for history.

• Pawel to push the message to TSC.

Byung shared proposal and we discussed it from Seccom requirements perspective. Special focus on packages upgrade for marketing release and the need to keep Seccom in the loop so if project is going to run subreleases, SECCOM is informed and can share update with latest packages upgrades recommendations coming from Nexus-IQ. Minor releases must be covered as well.

We might need a new tool for SCA that provides more open access for the project teams.

In case projects do not follow Global Requirements, this information must be transparently presented in the Release Notes.