[Weekly Meeting] [2024-07-19] Meeting Minutes #1393

tiagobento started this conversation in Weekly Meetings

tiagobento
Jul 19, 2024
Collaborator

Other topics

?

`10.0.x` stream (source for release 10.0.0 and subsequent patches. E.g., 10.0.1, 10.0.2)

Branches 10.0.x created! 🎉
Problems:
- Multiple wrong tags on Docker Hub.
  - 999.0.0 --> Should've been main
  - 999-snapshot --> Should've been main
  - 999-20240714 --> Should've been main-YYYYMMDD
  - 10.0 --> Shouldn't exist.. I guess it was already deleted?
  - 10.0.999-snapshot --> Should've been 10.0.x
  - 10.0.999-20240717 --> Should've been 10.0.x-YYYYMMDD
  - weekly-latest --> Should've been main-weekly-latest or 10.0.x-weekly-latest? Or delete it?
- Repositories that are not part of the release interfering with AUTOMATION A
  - incubator-kie-serverless-operator <-- (removed from 10.0.x branch)
  - incubator-kie-kogito-docs <-- (removed from 10.0.x branch)
  - incubator-kie-kogito-examples <-- (important for validation on PR checks etc)
  - incubator-kie-optaplanner-quickstarts <-- (important for validation on PR checks etc)
  - etc.
incubator-kie-kogito-images has the nightly pipelines disabled at the moment (also in main).
- @jstastny-cz will re-enable them for the 10.0.x branch.

How to make the 10.0.x stream completely independent from main?
- Or is it already?
  - @jstastny-cz They should be isolated already.
  - @jstastny-cz PR checks may be a little problematic because of our Jenkins.
    - Drools, OptaPlanner, and Kogito have GitHub Actions PR checks. Jenkins may be problematic when main diverges from 10.0.x.
    - incubator-kie-kogito-images doesn't have GitHub Actions PR checks, so relying on Jenkins may be problematic when main diverges from 10.0.x.
    - @pibizza Asked how to check if builds are healthy. @tiagobento replied doing a "full downstream build" on Drools would already test the downstream repos.
    - @tiagobento Asked if we could delete Jenkins PR checks for all repos that have PR checks on GitHub Actions as well. @jstastny-cz said we should do it for 10.0.x. @pibizza mentioned we should go to the mailing list first.
- What repos have the 10.0.x branch and are part of automations?
  - @jstastny-cz will double-check.

Release candidate - AUTOMATION D
- Release Procedure document: https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit#heading=h.69qvogh2xqsq
- Status:
  - @rodrigonull
    - updated all jobs to use the GPG keys.
    - update jobs to not have the promote jobs
    - update jobs to create the RC tags on GitHub
    - missing definition on which SVN credentials to use for uploading
    - plans to finish ^ by EOW next week
  - @jstastny-cz
    - not sure if anyone else other than @baldimir has permissions to drop artifacts from Nexus staging repo
    - once we have a stable RC build + artifacts we can call a vote

`main` stream (current source for next releases minor and major releases)

SonataFlow Operator Image published to Docker Hub
- https://hub.docker.com/r/apache/incubator-kie-sonataflow-operator/tags
- Where are those tags coming from?
  - main is probably from kie-tools?
  - 999.0.0 is coming from main of incubator-kie-serverless-operator. Probably latest too.
  - What about the others?
    - @rodrigonull submitted a PR removing builds from the incubator-kie-serverless-operator repo but it is still open.
- Why are we publishing them?
  - Reminiscent from when sonataflow-operator was not in kie-tools yet.
Removing SonataFlow Images and Operator from kie-tools
- ISSUE: Remove packages/sonataflow-images and packages/sonataflow-operator from kie-tools. #1040
- PR: kie-issues#1040: Remove packages/sonataflow-images and packages/sonataflow-operator from kie-tools incubator-kie-tools#2472
- ML THREAD: https://lists.apache.org/thread/ldb45nljq2q2d8pln3bxmh4g0m6k7o6l
- Duplicated "source of truth" for the SonataFlow Operator
- Disruption to the current, working setup
- @pibizza Suggested we can't discuss it without some key people like Walter.

Recoding

https://us06web.zoom.us/rec/share/5nuDLpE69tPEDP5XphYeNqv1GZqh4wQCu1Vr-JalBvQ6_JCbRth9k5HxngsswAqt.uHivO8JbUvC1Rf13
Passcode: @aBL.X8X

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment