Quarkus 3.31, released this month, will be the culmination of months of work making Quarkus applications builds faster. Learn more about it in this blog post by @gsmet.bsky.social: quarkus.io/blog/buildin...

Hello @spacefox.fr , j'essayais de te contacter pour discuter de ton article et ton générateur d'applications Quarkus mais tu n'es pas évident à débusquer, d'autant que ton GitLab a l'air down pour le moment :). Si tu as ce message, je veux bien que tu me contactes, merci !

#quarkus MCP server 1.1.0 is out! With progress, roots and sampling APIs... ⚡https://github.com/quarkiverse/quarkus-mcp-server/releases/tag/1.1.0

Believe it or not, the next release of Quarkus will be the 365th release since Quarkus became a thing, 6 years ago. It will be one year of release days! I released the large majority of them but this will change a bit with @janmartiska.bsky.social taking the responsibility for some LTS streams!

In 2016, I joined Red Hat to work on the Hibernate projects. At the end of 2018, I started working on a project that would become Quarkus. Soon, I will be joining IBM to continue my work on Quarkus. I truly believe Java has a bright future. It was already excellent and it's improving fast.

If you encounter a bug in Open Source software, don't live with it. Your future self will thank you: it will hit you at the worst moment. Assemble a reproducer, create an issue and more often than not, you'll get lucky. Here's to another example in the Quarkus project. github.com/quarkusio/qu...

For Quarkus, we often ask for simple reproducers when users report an issue. It might seem like wasted time for you but it's not. It happens often that the information is not enough to reproduce the issue and trying to guess how we can trigger the error is a massive waste of time on our time. 🧵

Wrapping 2024 on GitHub. If there was one thing to remember for next year: focus time is important and the longer the focus period, the most productive it is.