[wildfly-dev] Re: Request for feature team: updating WildFly to a specific version

Re the stability level, I'd like to explore the idea of using the server itself as the control point for what features are allowed by tools. 1) The WildFly Galleon Plug has stability notions that can be used when provisioning, to restrict the installation to functionality with a desired stability. Is this surfaced in Prospero? At the very beginning, Prospero of course comes before the installation, so there does need to be some initial control of stability that's not coming from the installation. 2) This feature is about updating an existing installation. That installation was provisioned with a particular minimum stability. Can this information be preserved in a way that allows Prospero to use it? I started down this line of thinking because there shouldn't be any need to start the JBoss CLI or HAL with a particular stability level in order to control the capabilities they expose to users. They connect to a server and can see its stability and can tailor their behavior accordingly. For example if a CLI command or command arg is at preview stability, don't offer it if the server is at community or default. On Thu, Mar 20, 2025 at 6:41 AM Bartosz Spyrko-Smietanko via wildfly-dev < wildfly-dev(a)lists.jboss.org&gt; wrote: -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His