Hi all,
Please find below the monthly meeting minutes from the last meeting
held on September 10th at 17:00 CEST.
Please don't hesitate to ask questions or reply with any corrections.
Best regards,
Serge Huber.
Board report
------------
- The Board again commented on a perceived lack of contributor
diversity.
- That perception may come from the high volume of merges and changes,
which generates more mail and can overshadow Jérôme's and Jonathan's
mailing-list activity.
- The delayed private-list send was a posting-address issue, not a
list outage. Serge Huber was sending from his Gmail address instead
of his apache.org address, so the private list refused the messages
and returned no bounce. He now uses his apache.org address more
systematically.
- The report was already sent, Serge asked for more feedback on the
reports as soon as they are prepared to make sure they are validated
before being sent.
PMC status for Jérôme
---------------------
- Discussion of Jérôme's access to private project channels, which is
needed for operational follow-up.
- The pull request Jérôme had been working on is done and merged on
the 3.0.x line. It still needs to be ported to master by Serge
Huber.
Versioning (3.x maintenance vs 4.0)
-----------------------------------
- Question raised: should the project open a 3.x maintenance branch
and move in-progress work onto a 4.x line, to leave room for future
3.x fixes?
- Context: some recent backports were not simple isolated patches.
- Technical point: Jahia's jExperience tests fail against the 3.1.x
snapshot because of breaking changes, and they need the 2.0
compatibility mode enabled.
- Possible impact of moving to 4.0:
- Main cost: revisit the website and docs already prepared for a
3.1 announcement.
- No in-principle objection was voiced in the meeting.
- Some users may be less inclined to adopt a 4.x release for a long
time. That creates an adoption risk and can split the community
and contributor effort across two lines. The project tries to
avoid that kind of split ("forking") as much as possible.
- Alternative: stay on 3.1 if the issues seen are mainly
configuration-related (compatibility mode).
- No final decision in the meeting. Further discussion is proposed on
this list.
Product hardening and report handling
-------------------------------------
- Ongoing hardening work continues, including automated and manual
review, with about 7 pull requests being finalized.
- Process reminders:
- Acknowledge official reports quickly, within 24 to 48 hours.
- Classify each item to choose the right handling: fix, docs, or
eventual announcement where appropriate.
- Tracking is still mostly local for now, for lack of convenient
private tickets.
- Open question: whether private GitHub Issues are available. This
needs to be verified.
- Distinction discussed: official ASF reporting channels (strict
timelines and obligations) versus other review channels (treated
more like engineering bugs).
- More automated and semi-automated reports targeting Apache projects
are expected. Continue handling them through the appropriate private
channels.
- Work continues on hardening optional APIs and endpoints, including
GraphQL, which is not enabled by default.
- Continued review of operator-facing customization and scripting
surfaces.
Proposed follow-ups
-------------------
- [Serge Huber] Port Jérôme's merged 3.0.x pull request to master.
- [Serge Huber] Finalize the hardening pull requests, especially the
GraphQL-related one (already backported; operational impact limited
because the feature is off by default).
- [Jonathan / Jérôme] Review the fix list and propose which items
should also land on the 3.0 line.
- [Jonathan / Jérôme] Test compatibility modes (including Jahia's
jExperience tests) and open tickets or issues if bugs are found.
- [Everyone] Share a position on this list on continuing with 3.1
versus considering 4.0. Proposed deadline: end of next week.
- [François] Confirm PMC enrollment and status (unclear in the
meeting).
- [Serge Huber] Ensure Jérôme has access to the latest private
follow-up material as needed.
- If no further input by the end of next week, the default proposal
remains shipping 3.1.
Regards,
