You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today all feature-packs WildFly Glow is discovering are put at the same level with respect to their maturity level. That is not reflecting the WildFly feature process in which some feature-packs could be incubating prior to reach the right stability level.
WildFly Glow should separate these feature-packs into groups, for example:
A user should be able to list the existing groups when calling the existing command: show-configuration
The text was updated successfully, but these errors were encountered:
jfdenise
changed the title
Introduce the notion of stability level Discovered feature-packs should be
Introduce the notion of stability level for discovered feature-packs
Sep 25, 2024
jfdenise
changed the title
Introduce the notion of stability level for discovered feature-packs
Introduce the notion of discovery group for discovered feature-packs
Sep 25, 2024
jfdenise
changed the title
Introduce the notion of discovery group for discovered feature-packs
Introduce the notion of discovery space for discovered feature-packs
Nov 25, 2024
jfdenise
added a commit
to jfdenise/wildfly-glow
that referenced
this issue
Nov 25, 2024
Today all feature-packs WildFly Glow is discovering are put at the same level with respect to their maturity level. That is not reflecting the WildFly feature process in which some feature-packs could be incubating prior to reach the right stability level.
WildFly Glow should separate these feature-packs into groups, for example:
The wildfly proposal: wildfly/wildfly-proposals#627
Implementation wise, the discovery-group name would be a branch in the https://github.com/wildfly/wildfly-galleon-feature-packs repository.
A user should be able to list the existing groups when calling the existing command:
show-configuration
The text was updated successfully, but these errors were encountered: