-
Notifications
You must be signed in to change notification settings - Fork 3
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
openidconnect 2.2.0 #241
Comments
Please make sure to create the release branch from the correct commit. I merged a bunch of prs which are not for this release. Thx |
Actually this commit should be fine |
Between 94fcbc3 From my POV, we can also have #243 in this release. |
regression reported: #246 |
Included in https://github.com/owncloud/openidconnect/releases/tag/v2.2.0-rc.2 - Thanks! |
include #254 |
Note: PR #222 added a parameter That class is used/extended in https://github.com/owncloud/msteamsbridge and so the code in that app needed a matching change. See issue https://github.com/owncloud/msteamsbridge/issues/37 which is fixed in PR https://github.com/owncloud/msteamsbridge/pull/36 I think that https://github.com/owncloud/msteamsbridge will need to be released "in sync" with https://github.com/owncloud/openidconnect (or some further code changes made somewhere that auto-detect what parameters to pass to the constructor or...) |
QA passed with several minor defects, see above. Cannot find code for #261 -- probably not yet implemented? |
Reason
Product approval
info.xml
description and screenshotQA
development
toqa
(testplan and tickets mentioned in release ticket)Documentation
Marketing
Build
All actions to be done on the release branch from here:
info.xml
(no version suffix)sonar-project.properties
(no version suffix)info.xml
info.xml
Beta/RC
v${version}-rc1
on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)v${version}-rc1
(see handbook for how to build)Final
v${version}
on release branchPublishing
#updates
channelPost-release
master
branch with description "Closes #XYZ" with the release ticket number$version
and close the milestoneThe text was updated successfully, but these errors were encountered: