Re: [DISCUSS] Component deprecation and codebase cleanup before 10.0.0

2023-12-19 Thread Mario Fusco
> drools has `drools-reliability` component which persistence is pluggable. > We have infinispan persistence and h2 persistence at the moment. If we want > to make the version 10 release "minimal", shall we keep only the h2 > persistence and then move the infinispan persistence to another repo >

Re: [DISCUSS] Component deprecation and codebase cleanup before 10.0.0

2023-12-19 Thread Francisco Javier Tirado Sarti
+1 On Tue, Dec 19, 2023 at 11:38 AM Tibor Zimányi wrote: > Hi, > > I think it is hard to compare with Spring Boot, because Spring is the most > used framework with much bigger market share than Quarkus. The focus on > Quarkus from the past (before KIE in Apache) was driven by internal company >

Re: [DISCUSS] Component deprecation and codebase cleanup before 10.0.0

2023-12-19 Thread Tibor Zimányi
Hi, I think it is hard to compare with Spring Boot, because Spring is the most used framework with much bigger market share than Quarkus. The focus on Quarkus from the past (before KIE in Apache) was driven by internal company decisions, not market share. But this is getting a bit off topic,

Re: [DISCUSS] Component deprecation and codebase cleanup before 10.0.0

2023-12-19 Thread Francisco Javier Tirado Sarti
Ricardo, for images I fully agree we should only include postgresql stuff. I think we need to separate the image content from the repo content. We can even select what we want to test in our CI, through maven profiles. What I want to avoid, given the changing priorities, is to remove some stuff

Re: [DISCUSS] Component deprecation and codebase cleanup before 10.0.0

2023-12-19 Thread Francisco Javier Tirado Sarti
Enrique, MongoDB data index persistence add-on is not a tech experiment, it is the technology that is used by one of the most active users in the Zulip community. Therefore, Mongo satisfies all the requirements you mention to stay, except being one of our primary company goals. Mongo per se is not

Re: [PROPOSAL] Finalizing Quarkus 3 migration + using fixed placeholder for snapshot versions

2023-12-19 Thread Luca Molteni
> On 13 Dec 2023, at 15:07, Mario Fusco wrote: > > It seems that we are finally ready to conclude the migration to Quarkus 3 and > the jakarta namespace. We're about to merge some last fixes in these hours, > so the plan is to wait the next nightly build and target tomorrow morning to >