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

Release Openidconnect 2.1.1 #208

Closed
35 of 42 tasks
IljaN opened this issue Feb 18, 2022 · 5 comments · Fixed by #216
Closed
35 of 42 tasks

Release Openidconnect 2.1.1 #208

IljaN opened this issue Feb 18, 2022 · 5 comments · Fixed by #216

Comments

@IljaN
Copy link
Member

IljaN commented Feb 18, 2022

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 tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
  • Create release branch with the format "release-$version"
  • Create "$version Testplan" -> [QA] 2.1.1 Testplan #210
  • copy new/reopened issues from the previous release ticket as 'Issues to review' below.
  • check if Non-normal Release Process applies, and adapt this checklist.

Documentation

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

Marketing

Build

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

  • Bump version in info.xml (no version suffix)
  • Bump "sonar.projectVersion=" in sonar-project.properties (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

  • Ping product owner to create github tag for v${version}-rc1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
  • Build and sign RC tarball from github tag v${version}-rc1 (see handbook for how to build)
  • Upload as Github release using changelog entries
  • Test and document in testplan + manual explorative testing:
    • If this is an enterprise app: Enabling the app must start the grace period
    • Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
    • Do changelog tests
    • Do regression tests
    • => 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

Publishing

  • Upload tarball to marketplace (see handbook in confluence for details)
  • Publish tarball for customers - old 10, old 10.0 and new portal (see handbook for details)
  • Send mail to release-coordination with link to this ticket and to the changelog
  • Copy email to rocket chat #updates channel

Post-release

@stijnbrouwers
Copy link
Contributor

This release should also include the fix for #194, right?

@IljaN
Copy link
Member Author

IljaN commented Feb 23, 2022

This release should also include the fix for #194, right?

Yes

@jnweiger jnweiger added this to the QA milestone Feb 25, 2022
@mmattel
Copy link
Contributor

mmattel commented Mar 10, 2022

With this upcoming release, is there anything docs relevant?

@IljaN
Copy link
Member Author

IljaN commented Mar 10, 2022

With this upcoming release, is there anything docs relevant?

Only bugfixes

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.

4 participants