[Weekly Meeting] [2024-06-28] Meeting Minutes

[porcelli]

• Blockers
  • Image used that does not exist
    • Remove unnecessary base image from quarkus examples (quay.io/kiegroup/kogito-runtime-jvm:latest) #1285
      • still missing:
  • Reproducible builds
    • Drools, Optaplanner, Runtimes, Apps: ok! @mariofusco
    • KIE Tools: PR open! @pefernan - fine to go!! kie-issues#1352: Enforce reproducible build on kie-tools incubator-kie-tools#2455
  • Incorporated reproducible build to -full profile!
  • Website updated (reproducible build requirement): https://kie.apache.org/docs/community/verify
  • Once KIE Tools is merged, @porcelli I'll Apache security
    • Ask about the ask about Release Manager trusted hardware ???
• Release Procedure
  • Automations verifications!
    • @pibizza and @mariofusco started the verification!
    • Only reading code, not with dry run...
      • we can try test branch for something other than 10... just to avoid
        • this will enable to check if it the pipelines will work
  • Dry runs...
    • Go for try if it works with 10? It's all revertible by @tiagobento
    • @porcelli raised concern to branch before having the missing pieces
    • @mariofusco mentioned that reading code to verify is not that productive, run it would be far more efficient
    • @jstastny-cz mentioned that branching automation could be tested right away
    • although we have credentials missing for SVN and gpg, we could start as soon the brokers are solved
    • as branching is part of the release procedure, @porcelli suggested that once we have the blockers merged... we go for a ML email that starts the release
• Logo
  • SonataFlow: colors updated with 3 new variations.. @ricardozanini will send a new mail to ML! probably last round!
• Activities on Operator
  • Unsure about the current state as part of the KIE Tools
    • would be good to get confirmation that what's there is functional