4th May 2026 - GitProxy Meeting Minutes #1508

Date

20260504- time

Meeting info

• Meeting link

• Register for future meetings

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

• Convene & roll call (5mins)
• Display FINOS Antitrust Policy summary slide and review Meeting Notices (see above)
• Approve past meeting minutes
  • 20th April 2026 - GitProxy Meeting Minutes #1506
• Make long-awaited 2.0 release?
• Release branching demo
  • Discuss: Cascade-based merging + which versions will be actively maintained?
• feat: Refreshed UI #1507 CI errors (dependencies, E2E tests, etc.)
• ...
• AOB, Q&A & Adjourn (5mins)

Meeting Minutes

• Approval of Previous Meeting Minutes

  • The minutes from the 20th April 2026 GitProxy Meeting (20th April 2026 - GitProxy Meeting Minutes #1506) were approved without objections.

• Make long-awaited 2.0 Release

  • Maintainers agreed the 2.0 release should proceed. @jescalada will create the version bump PR and notify via Slack for a second maintainer review/approval.
  • Awaiting additional maintainer sign-off due to UK bank holiday and reduced attendance.
  • Consensus to proceed with release; post-release feedback will be gathered.

• Release Branching Demo

  • @jescalada gave an overview and demo of automated release workflows, including cascade-based merging.
  • The concept of cascade merging (forward-porting) vs. cherry-picking (backporting) was discussed. Early feedback was positive; no objections were raised.
  • It was noted that supporting multiple major versions may be impractical, and deprecating 1.x after 2.0 was proposed for future consideration.
  • Agreed to continue discussion and seek wider input at the next meeting.

• Cascade-based Merging + Actively Maintained Versions

  • No final decision made on which versions will be actively maintained; more input from wider group requested.
  • The automation infrastructure is nearly ready to support either approach.

• feat: Refreshed UI feat: Refreshed UI #1507 CI errors (dependencies, E2E tests, etc.)

  • The UI refresh PR by @andypols has unresolved CI errors; @fabiovincenzi and @jescalada reviewed code, but did not resolve issues.
  • @fabiovincenzi will investigate CI failures and make suggestions or fixes as appropriate, or flag if too time-consuming.
  • Discussion included possible dependency/licensing issues due to new React dependencies.
  • The PR is not ready for merge; updates and fixes to be coordinated with @andypols.

• AOB, Q&A & Adjourn

  • Request raised to fix broken FinOS Slack and calendar invite links in README; workaround is to contact help@finos.org for Slack access.
  • No other business raised.

Action Items

• @jescalada: Create and submit PR for 2.0 version bump; notify team via Slack for approval.
• @re-vlad / @Andreybest: Confirm RC6 testing status and provide feedback at next meeting.
• @jescalada: Finalise and circulate release/branching process documentation PR for review.
• @fabiovincenzi: Investigate UI refresh (feat: Refreshed UI #1507) CI issues; propose fixes or suggestions.
• @grovesy: Update workflow/architecture roadmap and link related issues (New workflow architecture #1383, Architecture - Phase 1 - Creating room #1451).
• @kriswest: Keep "checkUserPushPermission" refactor on agenda for post-2.0; initiate technical discussion and document legacy issue.
• @kriswest: Coordinate merge plan/order for UI refresh and SSH/tag PRs; clarify Cypress test coverage.
• @RichardUri: Review dependency-check-plugin PR (feat: dependency-check-plugin #799) for adoptability/applicability.
• All: Tag priority issues without PRs for 2.2/roadmap triage before next meeting.
• @kriswest: Add documentation completeness to PR review checklist/template.
• All: Review SSH and tag push PRs for 2.1 milestone after 2.0 release.
• @jescalada: Fix FinOS Slack and calendar invite links in README, or escalate to FinOS admin.

Note: Some action items were rolled over from the previous meeting, as no progress was reported. The group agreed to keep the 2.0 release and branching automation topics open for further feedback/discussion.