[Weekly Meeting] [2024-07-12] Meeting Minutes

[tiagobento]

• @gitgabrio There's a PR that is breaking the reproducible build... (link?) we don't have enough files there to download from the CI to understand what is wrong.
• @gitgabrio Reinforcing that reproducible builds are not optional.
• @tiagobento said we shouldn't merge red PRs in general.
• @mariofusco said we sometimes did that in the past given flaky tests and urgency of merging something, but that's sub-optimal and somewhat improved recently.
• @tiagobento asked what should people do when there's a red PR in front of them... @pibizza mentioned that we should separate random infrastructure failures (e.g., GitHub Actions bugs, or network issues), and flaky tests or problems with the code itself. @gitgabrio said it is unrealistic to get all the tests passing, given their complexity.
• @tiagobento proposed we continue the discussion next week and send a "guideline" to the mailing list with a proposal
• @gitgabrio gave an idea to separate between tests that should always work, and tests that are potentially flaky due to their complicated nature (docker, timeouts etc)

Apache KIE 10 status

• @tiagobento's and @rodrigonull's public keys added to https://downloads.apache.org/incubator/kie/KEYS
• GPG signing keys configuration on Apache's Jenkins
  • NOTE: Still waiting on Apache infra on more information.
• GPG signing keys configuration on GitHub Actions (jitexecutor-native)
  • NOTE: Same as above.
• Replied Toshiya's comments on the Release Procedure document
• Paolo's checks of AUTOMATION A
  • NOTE: @pibizza Already explained by Jan and explained on Toshiya's slides
  • The commit message is different
    • (all)
  • It is unclear to me where the clone step is performed
    • (all)
  • It is unclear how the Automation B and C are connected.
    • (all)
  • There is an extra step for checking out the drools repo, that is also built during the step
    • (kogito-runtimes)
  • There is an extra step for checking out the drools and kogito-runtimes repos, that are also built in two successive steps
    • (kogito-apps)
    • NOTE: @tiagobento Could we remove those extra steps?
  • There is an extra step that validates the images and updates the modules descriptors.
    • (kogito-images)
  • What about [CHECK] Email for kie-tools?
    • NOTE: @tiagobento and @rodrigonull Can help @pibizza find the files to check it.
• Paolo's email thread about next steps
  • NOTE: Probably out of date now..
• ❓ What's missing for us to be able to branch out to 10.0.x?
  • NOTE: @rodrigonull Mentions we're good to go to the actual release because AUTOMATIONs A, B, and C are good.
  • NOTE: @rodrigonull Because we don't know how we're gonna sign artifacts, AUTOMATION D may still change a little.
  • NOTE: Nothing, @tiagobento will send an email proposing Tuesday (16-Jul-2024) as the date we go for it.

• @thiagoelg raised concerns about the Serverless Workflow packages on kie-tools... if they're gonna be part of the release or if someone has recently ran/built them? He'll create an email thread about this to have more people participate.

---

Recording

https://us06web.zoom.us/rec/share/iCj1X2iiTX1B88FIelBchJCunDpSV7Ap_uQzaKLBl8o_lxK_1S2O0e4NfMJoMVUZ.SIOM2PrUnJ9fKk3n
Passcode: h3*u3RFD