-
Notifications
You must be signed in to change notification settings - Fork 17
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
Release User LDAP 0.15.4 #605
Comments
use openldap docker. https://github.com/owncloud-docker/compose-playground/tree/master/compose#compose-playground
|
https://gitea.owncloud.services/security/user_ldap/pulls/1 should be included into the next release |
We'll push forward with the 0.15.3 release in the next week. I'd love to see a PR for this! |
@phil-davis the last 4 nightly builds for user_ldap failed. Is that random glitches, or something that needs fixing before we roll a release? |
That was due to some core changes to creating tags and related acceptance test changes that are not compatible with latest core 10.7.0. Fixed by owncloud/core#38784 - I expect to see green CI this morning. |
I opened one here: #636 |
If it needs to go into a special branch I can redirect the PR. |
@jnweiger CI was green for user_ldap last night - all good. |
Ready to go into RC. |
Release branch created. Tagged RC1. Prerelease at github https://github.com/owncloud/user_ldap/releases/tag/v0.15.3-rc1 |
Changelog Testing
Changelog testing passed. Manual regression testplan also passed (with (IMHO) non-blocker defects). |
Late fix appears after 0.15.3 was pushed to marketplace: #660
|
Tests with core 10.8.0-rc1 passed. See https://github.com/owncloud/enterprise/issues/4508#issuecomment-883398925 |
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)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 branch#marketing
channel to coordinate publishingPublishing
#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: