By Robert Deutz on 2023-07-25 09:00 in CMS Maintenance Team

Scheduled duration: 60min

Duration: 55 min

 

Participants: Christiane Maier-Stadtherr (Team Member), George Wilson (Team Member), Harald Leithner (Release Lead 5.0), Olivier Buisard (Release Manager 4.3), Richard Fath (Team Member), Robert Deutz (Team Leader), Shirielle Williams (Release Manager 4.3), Stefan Wendhausen (Translation Team), Viviana Menzel (Team Member)

 

Absent: Allon Moritz (Release Manager 4.4), Benjamin Trenkle (Production DC), David Jardin (Security Team Liaison), Fedir Zinchuk (Team Member), Hannes Papenberg (Automated Testing Team Liaison), Llewellyn van der Merwe (Team Member), Martin Kopp (Release Manager 4.4), Niels Braczek (Release Lead 5.0), Quy Ton (Team Member), Sigrid Gramlinger (CMS Release Team Liaison), Tobias Zulauf (Release Lead 3.10), Tuan Pham Ngoc (Team Member)

Meeting Results

Team lead election

We had two candidates and the result of the voting was quite close. The difference between the two candidates was that one thought it is running well and it doesn’t need so much change and the other one thought we need to change. Because of the voting results Robert wants to make clear that anyone can suggest changes and as long as that team supports it we can change whatever makes sense.

December Plan: “We see the number of open PRs are again getting higher. We need to work on this and the plan is that we meet bi-weekly at 7pm CEST to work on this.” - Do we want to push this to happen?

This was a decision made last year, but it never got implemented. The team agreed that we want to try it again. We want to do it weekly, it should be a fixed date in the week. The time should be used to discuss PR and work on PR. Robert will send out reminders so that nobody misses the date.  

 

Progress on b/c policy

No Progress on this so far.

 

Min/Max Version Support by Joomla Minor/Major Version for PHP Version, Browser Support, Mysql Support, Postgres Support
At the moment we publish a min version for our software stack. Publishing a max version would make it more clear what we are supporting. Unfortunately it is not a yes/no if we support a version. 

• Is it supporting a version when it works only when system messages are set to none?
• When we are in security mode, we only fix security relevant issues. Is something that comes with a new PHP Version and breaks the system a security fix?
• If we say we support 7.4 to 8.2, is this a good message in relation to marketing?  

We ended with the following:

When in security mode: 

• Fix all fatals. 
• Deprecations will be fixed where possible - but we will prioritise code stability if major code changes are required. 

In development mode: 

• Fix PHP bugs as soon as possible, we start testing our software from PHP beta versions like currentl
• We try to support all stable versions of our software stack

For the technical requirements page we will make a proposal to include a max version. Decision if we publish this will be made after we have the proposal. 

 

Bootstrap Support? Is it a b/c break to upgrade from 5.2 to 5.3 in a Joomla minor Version?
We are allowed to update the Bootstrap minor version in the Joomla minor version.

Playwright vs Cypress
We discussed this briefly and couldn’t say if the problems with the future of cypress are real or just a personal opinion of someone. Luckily it is not our decision.