-
Notifications
You must be signed in to change notification settings - Fork 157
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 5.3.0 #6620
Comments
SmokeTest against ocisbranch: v5.3.0-rc.3 Case 1: admin share folder(with file) to marie:Admin:
Marie:
Admin:
Marie:
Admin:
Marie:
Admin:
Case 2: admin share file to marie:Admin:
Marie:
Admin:
Marie:
Admin:
Case 3: admin create public links to folderAdmin:
Case 4: admin create link to fileAdmin:
Case 5: create new user:Admin:
Findings:there is nothing blocking release |
@ScharfViktor please wait a few moments more, we still have to add at least 1 pr before testing can start. |
Oops, that was a rush. Please ping me when it will be ready for smoke test. |
Tested the release candidate in combination with a patched app-provider (owncloud/ocis#3333), it works better than the completely broken state before somehow but I don't think there's a lot on the |
@ScharfViktor thanks for the testing, the accounts button link in settings is not an release blocker. |
sideCar mode tested and works, i didn't go into detail here because the oc10 app cover all other topics. |
Smoke test v5.3.0-rc.3 against oc10 app
Findings
No release blocker from my POV, let's ship as-is and publish another (bugfix) release soon |
Yes, sure. there in nothing that blocks release. |
Waiting for
Release checklist
release-5.3.0
@fschadepackages/web-integration-oc10/appinfo/info.xml
@fschadepackage.json
@fschadesonar-project.properties
@fschade.drone.env
to the most recent one from ocis master (let's see how it goes) @fschadedraft PR
for this branch @fschadev5.3.0-rc.1
from the release branch @pascalwengerterv5.3.0-rc.2
from the release branch @fschadev5.3.0-rc.3
from the release branchYYYY-MM-DD
to current date inchangelog/VERSION_YYYY-MM-DD
@pascalwengerterDraft a new Release
. Usev5.3.0
as a tag (the v prefix is important) and5.3.0
as name and publish it @pascalwengerterThe text was updated successfully, but these errors were encountered: