-
Notifications
You must be signed in to change notification settings - Fork 54
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
Code Review Item: Update Policy Needed #13
Comments
That sort of a policy would be very appealing to me, but I would make strong delineations between security fixes and ordinary patch/feature additions. I have a couple of orthogonal general package questions that I'll pose here. Please move the below to its own issue if you prefer that. I'm sure I'll come up with more later.
|
The images is just a basic deployment of the IdP that saves a deployer from having to install and config Jetty and the IdP. Backchannel is already setup too.
|
Makes sense and clarifies things, thanks. Since this is aimed at basic integration today, my follow-on questions fall in the category of "feature request" rather than "support considerations". I would still find the clarification you suggest, especially with regard to update releases versus security patches, very helpful. Thanks for taking the time. |
The Unicon IAM team did a code review and suggested several small adjustments. This is one of those adjustments:
To facilitate adoption of this image, Unicon should state a "policy" of how often checks for updates of the dependency resources (Java, Jetty, IdP) will occur and when those updates will be applied. The policy should include what type of updates will "trigger" an image release.
The text was updated successfully, but these errors were encountered: