Open chrisisla opened 8 months ago
FYI: @dschwartznyc , @manel-martos , @osttra-j-joyce, @eacunaISDA , @brianlynn2 , @nicholas-moger
Slides for meeting - CDM - Migration of the Release Process - Phase 1 29/01/2024 - 13:00 GMT
Agenda for kick-off meeting: Jan 29, 8-10 am EST, 1-3 pm GMT, 2-4 pm CEST, 6:30-8:30 pm IST
- Understand the current workflow
- Map and implement the current process in GitHub actions
- Document the on-process and off-process flows
- Run in parallel and confirm that the artifacts match
- Training
- Assign roles and responsibilities (ROTA)
- Cutover
- Review the current process, Minesh, 85 minutes (see https://github.com/finos/common-domain-model/files/14084405/CDM.Build.and.Release.Process.pptx)
- Next steps and wrap up, Dan, 5 minutes
Recap from the kick-off meeting Jan 29, 8-10 am EST, 1-3 pm GMT, 2-4 pm CEST, 6:30-8:30 pm IST
Comments and corrections are welcome.
In attendance (by name and GitHub Id or company): Arnau Oller (TradeHeader), Bramaramba Bhakthavatsalam (JPM), Brian Lynn (@brianlynn2), Chris Rayner (@chrisisla), Dan Schwartz (@dschwartznyc), Dhruva Sen Gupta (JPM), Eleonora Acuna (@eacunaISDA), Geogy Varughese (JPMC), Gerard Opazo (@gopazoTH), Harsha Valaturu (JPMC),James Joyce (@osttra-j-joyce), Manuel Martos (@manel-martos), Minesh Patel (@minesh-s-patel), Nicholas Moger (JPM), Pranabashish Deb (JPM),Tom Healey (@tomhealey-icma), Vishal P Naik (JPMC)
Agreed:
- main_clone
- SetProperties
- ReleaseProperties
- SnapshotProperties
Actions:
Notes: current experience is that it takes approximately 2 hours for the build process to run when there are no issues. The timing for resolution of issues depends on the nature of the problem.
The proposed workflow file has been pushed into the hosted repository. Find it here.
Recap and next steps from meeting # 2 - Mar 26, 9 AM EDT, 1 PM GMT, 2 PM CEST
Comments and corrections are welcome.
In attendance (by name and GitHub Id or company): Arnau Oller (TradeHeader), Brian Lynn (@brianlynn2), Chris Rayner (@chrisisla), Dan Schwartz (@dschwartznyc), Eleonora Acuna (@eacunaISDA), Gerard Opazo (@gopazoTH), Hugo Hills (@hugohills), Manuel Martos (@manel-martos), Tom Healey (@tomhealey-icma)
Recap:
Next steps:
Recap and next steps from meeting # 3 - Apr 10, 10 AM EDT, 3 PM BST, 4 PM CEST
Comments and corrections are welcome.
In attendance (by name and GitHub Id or company): Arnau Oller (TradeHeader), Brian Lynn (@brianlynn2), Chris Rayner (@chrisisla), Dan Schwartz (@dschwartznyc), Eleonora Acuna (@eacunaISDA), Gerard Opazo (@gopazoTH), Manuel Martos (@manel-martos), Minesh Patel (@minesh-s-patel), Tom Healey (@tomhealey-icma)
Recap:
Next steps:
Contribution improvements agreed on meeting # 4 Apr 29 Source PR
Recap and next steps from meeting # 4 - Apr 29, 9 AM EDT, 2 PM BST, 3 PM CEST
Comments and corrections are welcome.
In attendance (by name and GitHub Id or company): Arnau Oller (TradeHeader), Brian Lynn (@brianlynn2), Chris Rayner (@chrisisla), Dan Schwartz (@dschwartznyc), Eleonora Acuna (@eacunaISDA), Hugo Hills (@hugohills-regnosys), Manuel Martos (@manel-martos), Tom Healey (@tomhealey-icma). Apologies: MInesh Patel (@minesh-s-patel)
Open question:
Next steps:
As discussed in the TAWG meeting on July 11 , due to challenges in engagement this project is on hold.
Under various branches, the repo mentioned above is current with work to date.
The next steps will be to finalize and test the changes based on agreement on how to address the open questions including those listed below:
For reference, participants in the project (by name and GitHub Id or company): Arnau Oller (TradeHeader), Brian Lynn (@brianlynn2), Chris Rayner (@chrisisla), Dan Schwartz (@dschwartznyc), Eleonora Acuna (@eacunaISDA), Hugo Hills (@hugohills-regnosys), Manuel Martos (@manel-martos), MInesh Patel (@minesh-s-patel),Tom Healey (@tomhealey-icma).
As agreed in the meeting of the CDM Technology Architecture Working Group on November 9th (#2484) the next initiative to be undertaken by the group is to migrate the existing release process from codefresh to github actions. This should make the release process more transparent to the community, and allow a broader group of the CDM maintainers to execute the process.
This Issue describes the scope that we will be using for the project.
In Scope
Out of Scope
These are all out of scope for this project. These can be considered and addressed in future phases of work.
If you have any comments or suggested changes to the scope then please add a comment to this Issue and they will be considered for inclusion.