Hi Fabrizio, as this is very crucial PR, I can imagine also we 'block' PRs that contain patternfly changes until the big PF4 -> PF5 PR is merged. I can imagine this only if we are confident enough PF4 -> PF5 PR will be merged in a week? or two weeks? Not sure what should be such 'blocking window' size.
Personally, I can not imagine we do similar 'blocking window' longer than two weeks. Ideal 'blocking window' size doesn't exist for sure. We would probably agree - the shorter the better. Jozef Marko Software Developer [email protected] ________________________________ From: Fabrizio Antonangeli <[email protected]> Sent: Tuesday, April 1, 2025 4:00 PM To: [email protected] <[email protected]> Subject: [EXTERNAL] [PROPOSAL] Coordinating PatternFly 5 Upgrade Effort Hello all, Aditya and I are very close to finishing a PR for updating PatternFly to v5 [1]. The main problem we have is that while we update, fix issues, and run the CI, the work on the main branch using PF4 continues. This means we have to continuously sync our PR, update the new code to PF5, re-test, and check the CI. The CI also takes time to run, as all frontend packages use PatternFly, and the CI tests all of them. Once everything is green, reviewers may also need time to go through the PR (which includes 530 files), while in the meantime, PF4 development on `main` continues. Since I don't think we can freeze PF4 work until the PF5 update is completed, my suggestion is to establish a temporary "rule": Anyone developing PF4 code on main should also open a PR on Aditya's `allpackagesp4top5` branch with the corresponding PF5 update. This would be required only until the PR is reviewed and merged. Alternatively, can we "split" our work into SWF-related updates and Online Editor-related work? As always, I'm open to other ideas. [1] https://github.com/apache/incubator-kie-tools/pull/2853 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
