Skip to content

Commit bff9d68

Browse files
actions-useractions-user
committed
Sync working groups
1 parent cfacc7d commit bff9d68

File tree

1 file changed

+64
-64
lines changed

1 file changed

+64
-64
lines changed

‎_data/wg.yaml‎

Lines changed: 64 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,69 @@
11
---
22
working-groups:
3+
- title: "Panache.Next"
4+
board-url: "https://github.com/orgs/quarkusio/projects/50"
5+
short-description: |
6+
The primary objective of this working group is to develop the next version of Panache.
7+
readme: |
8+
<h1>Objective</h1>
9+
<p>The main objective of this working group is to bring forth the next version of Panache.</p>
10+
<h1>The Problem</h1>
11+
<p>Panache is great for many things, but over time, we realised the following limitations:</p>
12+
<ul>
13+
<li>We have three distinct versions: Hibernate ORM, Hibernate Reactive and Mongo (blocking and reactive)</li>
14+
<li>It is impossible to use the same entities with Hibernate ORM and Hibernate Reactive</li>
15+
<li>Stateless sessions are not supported</li>
16+
<li>Hibernate Processor annotations, and Jakarta Data are not supported</li>
17+
<li>We have triplicate types such as <code>Sort</code> and <code>Order</code> between Panache, ORM and Jakarta Data</li>
18+
<li>We have two ways to place entity query operations : on the entity itself, or in repositories</li>
19+
<li>Entity query operations require type-system hacks which makes them less type-safe than we want with <code>var</code> and <code>for-each</code> and especially with reactive operations.</li>
20+
</ul>
21+
<h1>The proposed Solution</h1>
22+
<p>We propose a new Panache version that will solve all these issues:</p>
23+
<ul>
24+
<li>Unify all variants in a single module, supporting blocking, reactive, stateless and stateful sessions</li>
25+
<li>Provide an entity toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
26+
<li>Move all entity query operations from the entity class to the repository class</li>
27+
<li>Provide a repository toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
28+
<li>Provide easy access to any type of repository by placing them as nested interfaces in the entity class, via a generated accessor on the entity metamodel class</li>
29+
<li>Provide out of the box accessors for the 4 modes of operation repositories on the entity metamodel class</li>
30+
<li>Support Jakarta Data and Hibernate Processor type-safe annotations</li>
31+
<li>Optional: Support of Mongo via the coming ORM JDBC support</li>
32+
<li>Optional: provide JD repository type alternatives for the missing three modes</li>
33+
<li>Optional: provide a way to convert Panache 1 to Panache.Next</li>
34+
</ul>
35+
<h1>Definition of Done</h1>
36+
<ul>
37+
<li>Deliver the new Panache extension as a <code>stable</code> state (after preview/experimental versions for feedback)</li>
38+
<li>Tests</li>
39+
<li>Documentation</li>
40+
<li>Codestart</li>
41+
<li>REST Data with Panache support</li>
42+
<li>Renarde support</li>
43+
<li>Quarkus Insights</li>
44+
</ul>
45+
<h1>Scope of Work</h1>
46+
<p>It is currently out of scope to retrofit this with the existing Panache modules. This will be a new module with no backward compatibility (although most type-unsafe operations will continue as-is, so you will be familiar with them).</p>
47+
<h1>Organizing the Work</h1>
48+
<h2>Communication and Transparency:</h2>
49+
<p>This will be done via GitHub issues on the Quarkus core project.</p>
50+
<h2>Expected Timeline:</h2>
51+
<p>Most of the R&amp;D and design work has been completed over the last two years. Now remains the task of merging, documenting, testing, and tweaking it until it's complete.</p>
52+
<ul>
53+
<li>Point of contact: @FroMage (@<strong>Stephane Epardaud</strong> on Zulip)</li>
54+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/48949</li>
55+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261">Zulip</a></li>
56+
</ul>
57+
status: on track
58+
lts: false
59+
completed: false
60+
last-activity: 2025-10-07
61+
last-update-date: 2025-09-08
62+
last-update: |
63+
On track, @FroMage is still working on Panache 2.
64+
point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)"
65+
proposal: https://github.com/quarkusio/quarkus/discussions/48949
66+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261
367
- title: "Gizmo 2"
468
board-url: "https://github.com/orgs/quarkusio/projects/43"
569
short-description: |
@@ -140,70 +204,6 @@ working-groups:
140204
point-of-contact: "@edeandrea, @aureamunoz , @mkouba"
141205
proposal: https://github.com/quarkusio/quarkus/discussions/49964
142206
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Spring-Style.20Testing.20Compatibility.20for.20Quarkus/with/539471996
143-
- title: "Panache.Next"
144-
board-url: "https://github.com/orgs/quarkusio/projects/50"
145-
short-description: |
146-
The primary objective of this working group is to develop the next version of Panache.
147-
readme: |
148-
<h1>Objective</h1>
149-
<p>The main objective of this working group is to bring forth the next version of Panache.</p>
150-
<h1>The Problem</h1>
151-
<p>Panache is great for many things, but over time, we realised the following limitations:</p>
152-
<ul>
153-
<li>We have three distinct versions: Hibernate ORM, Hibernate Reactive and Mongo (blocking and reactive)</li>
154-
<li>It is impossible to use the same entities with Hibernate ORM and Hibernate Reactive</li>
155-
<li>Stateless sessions are not supported</li>
156-
<li>Hibernate Processor annotations, and Jakarta Data are not supported</li>
157-
<li>We have triplicate types such as <code>Sort</code> and <code>Order</code> between Panache, ORM and Jakarta Data</li>
158-
<li>We have two ways to place entity query operations : on the entity itself, or in repositories</li>
159-
<li>Entity query operations require type-system hacks which makes them less type-safe than we want with <code>var</code> and <code>for-each</code> and especially with reactive operations.</li>
160-
</ul>
161-
<h1>The proposed Solution</h1>
162-
<p>We propose a new Panache version that will solve all these issues:</p>
163-
<ul>
164-
<li>Unify all variants in a single module, supporting blocking, reactive, stateless and stateful sessions</li>
165-
<li>Provide an entity toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
166-
<li>Move all entity query operations from the entity class to the repository class</li>
167-
<li>Provide a repository toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
168-
<li>Provide easy access to any type of repository by placing them as nested interfaces in the entity class, via a generated accessor on the entity metamodel class</li>
169-
<li>Provide out of the box accessors for the 4 modes of operation repositories on the entity metamodel class</li>
170-
<li>Support Jakarta Data and Hibernate Processor type-safe annotations</li>
171-
<li>Optional: Support of Mongo via the coming ORM JDBC support</li>
172-
<li>Optional: provide JD repository type alternatives for the missing three modes</li>
173-
<li>Optional: provide a way to convert Panache 1 to Panache.Next</li>
174-
</ul>
175-
<h1>Definition of Done</h1>
176-
<ul>
177-
<li>Deliver the new Panache extension as a <code>stable</code> state (after preview/experimental versions for feedback)</li>
178-
<li>Tests</li>
179-
<li>Documentation</li>
180-
<li>Codestart</li>
181-
<li>REST Data with Panache support</li>
182-
<li>Renarde support</li>
183-
<li>Quarkus Insights</li>
184-
</ul>
185-
<h1>Scope of Work</h1>
186-
<p>It is currently out of scope to retrofit this with the existing Panache modules. This will be a new module with no backward compatibility (although most type-unsafe operations will continue as-is, so you will be familiar with them).</p>
187-
<h1>Organizing the Work</h1>
188-
<h2>Communication and Transparency:</h2>
189-
<p>This will be done via GitHub issues on the Quarkus core project.</p>
190-
<h2>Expected Timeline:</h2>
191-
<p>Most of the R&amp;D and design work has been completed over the last two years. Now remains the task of merging, documenting, testing, and tweaking it until it's complete.</p>
192-
<ul>
193-
<li>Point of contact: @FroMage (@<strong>Stephane Epardaud</strong> on Zulip)</li>
194-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/48949</li>
195-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261">Zulip</a></li>
196-
</ul>
197-
status: on track
198-
lts: false
199-
completed: false
200-
last-activity: 2025-09-22
201-
last-update-date: 2025-09-08
202-
last-update: |
203-
On track, @FroMage is still working on Panache 2.
204-
point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)"
205-
proposal: https://github.com/quarkusio/quarkus/discussions/48949
206-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261
207207
- title: "Java 25 support"
208208
board-url: "https://github.com/orgs/quarkusio/projects/59"
209209
short-description: |

0 commit comments

Comments
 (0)