Skip to content

Commit cc8bf68

Browse files
actions-useractions-user
committed
Sync working groups
1 parent a951b34 commit cc8bf68

File tree

1 file changed

+74
-74
lines changed

1 file changed

+74
-74
lines changed

‎_data/wg.yaml‎

Lines changed: 74 additions & 74 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,79 @@
11
---
22
working-groups:
3+
- title: "Java 25 support"
4+
board-url: "https://github.com/orgs/quarkusio/projects/59"
5+
short-description: |
6+
The objective of this working group is to enable Quarkus applications to run cleanly across dev/test/production modes on Java 25, with no requirement to adopt Java 25 as a baseline.
7+
readme: |
8+
<h3>Objective</h3>
9+
<p>To enable Quarkus applications to run cleanly across dev/test/production modes on Java 25, with no requirement to adopt Java 25 as a baseline.</p>
10+
<h3>The Problem</h3>
11+
<p>Java 25 brings new features and platform-level changes (e.g., new JEPs, VM flags, performance tweaks) that may trigger warnings, break behavior, or degrade Quarkus experiences. Dependencies or extensions may also face compatibility challenges. A coordinated effort is needed to identify, fix, document, and optionally leverage these changes.</p>
12+
<h3>The Solution</h3>
13+
<p>The working group will:</p>
14+
<ul>
15+
<li>Attempt to run representative Quarkus applications under Java 25 in dev, test, and production modes.</li>
16+
<li>Catalog issues, warnings, or incompatibilities in a Wiki or issue tracker.</li>
17+
<li>Propose and implement fixes or mitigations (or document workarounds).</li>
18+
<li>Optionally explore beneficial Java 25 features (e.g., Scoped Values, Flexible Constructor Bodies), without requiring their use.</li>
19+
<li>Identify and remediate or flag problematic Quarkus extensions.
20+
⠀</li>
21+
</ul>
22+
<h3>Definition of Done</h3>
23+
<ul>
24+
<li>Publish a wiki page detailing issues and resolutions.</li>
25+
<li>Ensure Quarkus core and its ecosystem can operate cleanly under Java 25 in all modes.</li>
26+
<li>Integrate any selected Java 25 features in an optional, non-breaking manner.</li>
27+
<li>Document or fix problematic extensions, offering guidance where needed.</li>
28+
<li>Communicate results via a blog post or quarkus-dev announcement.
29+
⠀</li>
30+
</ul>
31+
<h3>Scope of Work</h3>
32+
<p><strong>In scope:</strong></p>
33+
<ul>
34+
<li>Running and diagnosing Quarkus on Java 25.</li>
35+
<li>Fixing issues in Quarkus core repository and extensions.</li>
36+
<li>Exploring select Java 25 enhancements.</li>
37+
</ul>
38+
<p>⠀
39+
<strong>Out of scope:</strong></p>
40+
<ul>
41+
<li>Mandating Java 25 as the minimum supported runtime.</li>
42+
</ul>
43+
<p>⠀</p>
44+
<h3>Organizing the Work</h3>
45+
<ol>
46+
<li><strong>Communication &amp; Transparency:</strong>
47+
<ul>
48+
<li>Use GitHub discussion, project board, and issues.</li>
49+
<li>Coordinate via Quarkus Zulip and GitHub.</li>
50+
</ul>
51+
</li>
52+
<li><strong>Timeline &amp; Milestones:</strong>
53+
<ul>
54+
<li><strong>Exploration Phase:</strong> Run tests on Java 25 Candidate Release, document findings before GA (target: <em>before September 16, 2025</em>), so we can guide our users as soon as Java 25 reaches GA.</li>
55+
</ul>
56+
</li>
57+
</ol>
58+
<hr />
59+
<ul>
60+
<li>Point of contact: @Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)</li>
61+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/49696</li>
62+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat">Zulip</a></li>
63+
</ul>
64+
status: on track
65+
lts: false
66+
completed: false
67+
last-activity: 2025-11-03
68+
last-update-date: 2025-10-27
69+
last-update: |
70+
In the last month, the WG - Java 25 support did not close any issues but opened a new issue focused on providing container images for Java 25. This activity aligns with the group's objective of ensuring Quarkus applications can run seamlessly across various modes on Java 25, without requiring it as a baseline.
71+
The container image should be available in november.
72+
73+
(This status update was automatically generated using AI.)
74+
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
75+
proposal: https://github.com/quarkusio/quarkus/discussions/49696
76+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
377
- title: "OIDC improvements"
478
board-url: "https://github.com/orgs/quarkusio/projects/46"
579
short-description: |
@@ -561,80 +635,6 @@ working-groups:
561635
last-update-date: 2025-04-01
562636
last-update: |
563637
In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
564-
- title: "Java 25 support"
565-
board-url: "https://github.com/orgs/quarkusio/projects/59"
566-
short-description: |
567-
The objective of this working group is to enable Quarkus applications to run cleanly across dev/test/production modes on Java 25, with no requirement to adopt Java 25 as a baseline.
568-
readme: |
569-
<h3>Objective</h3>
570-
<p>To enable Quarkus applications to run cleanly across dev/test/production modes on Java 25, with no requirement to adopt Java 25 as a baseline.</p>
571-
<h3>The Problem</h3>
572-
<p>Java 25 brings new features and platform-level changes (e.g., new JEPs, VM flags, performance tweaks) that may trigger warnings, break behavior, or degrade Quarkus experiences. Dependencies or extensions may also face compatibility challenges. A coordinated effort is needed to identify, fix, document, and optionally leverage these changes.</p>
573-
<h3>The Solution</h3>
574-
<p>The working group will:</p>
575-
<ul>
576-
<li>Attempt to run representative Quarkus applications under Java 25 in dev, test, and production modes.</li>
577-
<li>Catalog issues, warnings, or incompatibilities in a Wiki or issue tracker.</li>
578-
<li>Propose and implement fixes or mitigations (or document workarounds).</li>
579-
<li>Optionally explore beneficial Java 25 features (e.g., Scoped Values, Flexible Constructor Bodies), without requiring their use.</li>
580-
<li>Identify and remediate or flag problematic Quarkus extensions.
581-
⠀</li>
582-
</ul>
583-
<h3>Definition of Done</h3>
584-
<ul>
585-
<li>Publish a wiki page detailing issues and resolutions.</li>
586-
<li>Ensure Quarkus core and its ecosystem can operate cleanly under Java 25 in all modes.</li>
587-
<li>Integrate any selected Java 25 features in an optional, non-breaking manner.</li>
588-
<li>Document or fix problematic extensions, offering guidance where needed.</li>
589-
<li>Communicate results via a blog post or quarkus-dev announcement.
590-
⠀</li>
591-
</ul>
592-
<h3>Scope of Work</h3>
593-
<p><strong>In scope:</strong></p>
594-
<ul>
595-
<li>Running and diagnosing Quarkus on Java 25.</li>
596-
<li>Fixing issues in Quarkus core repository and extensions.</li>
597-
<li>Exploring select Java 25 enhancements.</li>
598-
</ul>
599-
<p>⠀
600-
<strong>Out of scope:</strong></p>
601-
<ul>
602-
<li>Mandating Java 25 as the minimum supported runtime.</li>
603-
</ul>
604-
<p>⠀</p>
605-
<h3>Organizing the Work</h3>
606-
<ol>
607-
<li><strong>Communication &amp; Transparency:</strong>
608-
<ul>
609-
<li>Use GitHub discussion, project board, and issues.</li>
610-
<li>Coordinate via Quarkus Zulip and GitHub.</li>
611-
</ul>
612-
</li>
613-
<li><strong>Timeline &amp; Milestones:</strong>
614-
<ul>
615-
<li><strong>Exploration Phase:</strong> Run tests on Java 25 Candidate Release, document findings before GA (target: <em>before September 16, 2025</em>), so we can guide our users as soon as Java 25 reaches GA.</li>
616-
</ul>
617-
</li>
618-
</ol>
619-
<hr />
620-
<ul>
621-
<li>Point of contact: @Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)</li>
622-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/49696</li>
623-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat">Zulip</a></li>
624-
</ul>
625-
status: on track
626-
lts: false
627-
completed: false
628-
last-activity: 2025-10-13
629-
last-update-date: 2025-10-27
630-
last-update: |
631-
In the last month, the WG - Java 25 support did not close any issues but opened a new issue focused on providing container images for Java 25. This activity aligns with the group's objective of ensuring Quarkus applications can run seamlessly across various modes on Java 25, without requiring it as a baseline.
632-
The container image should be available in november.
633-
634-
(This status update was automatically generated using AI.)
635-
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
636-
proposal: https://github.com/quarkusio/quarkus/discussions/49696
637-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
638638
- title: "Gizmo 2"
639639
board-url: "https://github.com/orgs/quarkusio/projects/43"
640640
short-description: |

0 commit comments

Comments
 (0)