Incubating Features in Hibernate 6

If you tried Hibernate 6, you might have recognized the new @Incubating annotation. The Hibernate team introduces it to tell users about new APIs and interfaces that might still change. That’s a great addition because most developers expect new APIs and features to be stable after they are part of a final release. In general, that is the case. Hibernate’s APIs are incredibly stable. But not being able to change a new API after its 1st release makes it impossible to improve it based on user feedback. It also makes it hard to develop and release a set of interconnected features. So, allowing a little more flexibility might be good for everyone involved.
The new @Incubating annotation gives Hibernate’s development team this flexibility. By annotating a configuration parameter or interface with @Incubating, the team warns their users that this feature might still change. Hibernate 6’s release stated that they, of course, aim to keep these APIs stable. But pending work on other features or user feedback might cause a few changes in the future.
From now on, you should keep an eye on Hibernate’s incubation report and double-check if a newly introduced feature is based on interfaces, classes, or configuration parameters annotated with @Incubating. If that’s the case, you can still use them. But you should be aware that a future release might introduce a change that could affect your code.
Links mentioned in the video:
thorben-jansse...
in.relation.to...
docs.jboss.org...
thorben-jansse...
thorben-jansse...
thorben-jansse...
thorben-jansse...
thorben-jansse...
thorben-jansse...
thorben-jansse...
Like my channel? Subscribe!
➜ bit.ly/2cUsid8
Read the accompanying post: thorben-jansse...
Want to connect with me?
Blog: thorben-jansse...
Twitter: / thjanssen123
Facebook: / thorbenjanssenofficial
Linkedin: / thorbenjanssen