Quarkus 1.x had a single universal platform which helped us keep things simple and uniform across tools/docs but had certain limits:

1) tools could only add/present extensions that was available in the released platform - not find non-platform extensions

2) when used the referenced BOM is massive and applies version lockdowns of dependencies even if the user does not use such dependency through quarkus

3) everyone participating in the platform in practice had to be ready to released and update at the same time.

To fix this we are doing a few things:

• introducing a registry.quarkus.io for all devtools to consult for looking up platform and extensions
• introduce bom generator in platform that generates uniform but composable BOMs that can be imported individually rather than all in bulk
• introduce notion of platform stream to indicate which minor version you are tracking and/or what you want to target when using tools