[oniro-dev] IT meeting@EclipseCon 2022 meeting minutes

[Andrei Gherzan <andrei.gherzan@xxxxxxxxxx>]

Who?

Agustin, Alberto, Andrei, Denis, Frederic, Luca, Sebastien (over Zoom), Stefan

 

What?

1. Tag signing for the release

• We want to gpg sign the release git tags for the coming up release.
• EF doesn't have this as a common practice for other projects but can handle it manually for Oniro - it wouldn't require much effort.
• The plan is for Oniro to tag (unsigned) the release and during the release community review, these tags are to be replaced by IT with an identical but signed set of tags (multiple repositories).
• No binaries are involved in this process for this release - only source signing via git tags.

1. #2081 (merge/push fails)

• We discussed having faster feedback on ECA issues while implementing it as a pipeline job. In this way and eventual issues will not only surface at merge time but also sooner when CI validates the incoming branch.
• An issue was created in GitLab for implementing this (https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/it-services-oniro-wg/pipelines-architecture-oniro-wg/-/issues/55). The idea was to use the ECA API as part of or similar to how we deal with the DCO check.

1. Status updates for GitLab upgrades

• Planned maintenance is advertised via https://www.eclipsestatus.io/. Subscription is possible to keep track of these activities.
• This is usually also sent to the committer mailing list (but was missed last time).
• EF IT uses two planned maintenance windows that are out of normal working hours.

1. Having an easy way to filter for Oniro issues in the helpdesk repository

• The current plan of using a '[Oniro]' subject prefix is not feasible anymore as the upgrade doesn't allow for "[]" characters in the filter. To be investigated by EF IT.
• Labels were proposed but not considered at this moment as having 400+ project labels would make applying labels a convoluted process.

1. Changing EF account email

• Additional accounts are to be used only when multiple identities are actively used.
• When changing association, the ECA is revoked but even cherry-picks of old commits should pass ECA (and DCO). This is because when cherry-picking, the committer will change and ECA checks the committer against the account email.

1. IT compliance pipelines migration

• Migration from OSTC to Noi Techpark has been completed and no issues were encountered.
• Two main components in the scope of this migration: a Fossology instance and a GitLab runner.
• As planned before, the actual migration to EF of any of the current pipelines is to be completed after the release to avoid impact on the release timeline.
• We could split some non-functional pipeline changes that would aid the migration later (refactoring the current pipeline migration MRs).

 

Regards,

Andrei