-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add admin client requirements to the process #600
Conversation
9d8f4e5
to
3728a73
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @darranl. I'll leave merging this to you as you know what other feedback you want.
FEATURE_PROCESS.adoc
Outdated
| *Admin Clients* | ||
(HAL / JBoss CLI) | ||
|
||
| Management model changes must be compatible with the lowe level model |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lowe? you mean lowest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, I have fixed this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @darranl
… moving away from embedded comments.
3728a73
to
c5a443f
Compare
I just sent a message to the dev list, I think will give it one more day then merge. Being merged does not set it in stone so we can still evolve as feedback comes in / we try and work with these contraints. |
The updates I am proposing here relate to how in general the admin clients should be considered when new features are added to the application server.
The admin clients are maintained by smaller teams within the overall WildFly team, for this reason it is not going to scale if every feature requires complete admin client integration at every stability level so the general premise behind this proposal is that features can be added at Experimental or Preview level with a reduced set of admin client requirements, the admin clients can then continue to evolve to add these features and then the underlying feature can be promoted to Community / Default.
Note: This is not so much about features being added directly to the admin clients at the stability levels as in that case the admin client developer is already in control of compatibility etc...