Skip to content
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

encryption 1.5.1 #262

Closed
31 of 39 tasks
jnweiger opened this issue Apr 27, 2021 · 3 comments · Fixed by #291
Closed
31 of 39 tasks

encryption 1.5.1 #262

jnweiger opened this issue Apr 27, 2021 · 3 comments · Fixed by #291
Assignees
Milestone

Comments

@jnweiger
Copy link
Contributor

jnweiger commented Apr 27, 2021

Reason

Product approval

  • Verify transifex commits are in master: If a folder https://github.com/owncloud//tree/master/l10n exists, then https://drone.owncloud.com/owncloud/ should receive nightly '[tx] updated from transifex` ...
  • Ping pmaier to check info.xml description and screenshot
  • Get approval on translations from pmaier - send the date of the last tx commit from drone to Patrick

QA

  • Create QA Milestone and set the description to $version
  • Move items from development to qa
  • Create release branch with the format "release-$version"
  • Create "$version Testplan" (QA templates) -> [QA] 1.5.1 Testplan #263
  • copy new/reopened issues from the previous release ticket as 'Issues to review' below.

Documentation

  • Changes in the docs needed? If so create issue in owncloud/docs.

Marketing

  • Ping @owncloud/marketing
  • Request App image if app is new or changed fundamentally

Build

All actions to be done on the release branch from here:

  • Bump version in info.xml (no version suffix)
  • Check php version dependency in info.xml
  • Check minimum ownCloud version dependency in info.xml
  • Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

  • Create github tag for v${version}RC1 on release branch
  • Build and sign RC tarball from github tag v${version}RC1 (see
    handbook for how to build)
  • Upload as Github release using changelog entries
  • Manual explorative testing:
    • If this is an enterprise app: Enabling the app must start the grace period
    • If this is the initial release of an app: Check that the minimum version constraint resolves correctly
    • Changelog testing
    • Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

  • Check that no documentation issues are pending
  • Rename last RC tarball to final
  • Create github tag for final v${version} on release branch
  • Upload as Github release using changelog entries
  • Ping #marketing channel to coordinate publishing

Publishing

Not done. Encryption is special.

  • Upload tarball to marketplace (see handbook in confluence for details)
  • Publish tarball for customers (see handbook in confluence for details) - https://customer.owncloud.com and https://portal.owncloud.com
  • Send mail to release-coordination with link to this ticket and to the changelog
  • Copy email to rocket chat #updates channel

Post-release

@jnweiger jnweiger added this to the QA milestone Apr 27, 2021
@jnweiger jnweiger pinned this issue Apr 27, 2021
@jnweiger jnweiger modified the milestones: QA, 10.8.0 Apr 29, 2021
@jnweiger
Copy link
Contributor Author

jnweiger commented Jun 7, 2021

Issues opened while testing

@mmattel
Copy link
Contributor

mmattel commented Jun 8, 2021

owncloud/docs#3636 --> merged and backported

@jnweiger
Copy link
Contributor Author

jnweiger commented Jun 21, 2021

Changelog testing done as part of #263 (comment)

  • hsmdaemon does both legacy base64 and new binary encoding, just fine.
  • occ fix-encrypted-version prints messages "No fix found ..., restored version to original" e.g. for unencrypted files.

@jnweiger jnweiger unpinned this issue Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants