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 search_elastic 2.4.0 #323

Closed
39 of 46 tasks
phil-davis opened this issue May 23, 2023 · 4 comments · Fixed by #337
Closed
39 of 46 tasks

Release search_elastic 2.4.0 #323

phil-davis opened this issue May 23, 2023 · 4 comments · Fixed by #337
Projects
Milestone

Comments

@phil-davis
Copy link
Contributor

phil-davis commented May 23, 2023

Reasons

Note: the change in that PR also works fine with server core 10.12 and before, so there should be no need to bump the core min-version.

The app can be released any time before 10.13 - it should work fine with any of the recent oC10 core releases.

Full testplan needed

Product approval

  • Verify transifex commits (enterprise should update weekly, others daily): If folder l10n exists, then git log should show '[tx] updated from transifex` ...
  • Ping ProductManagement to check info.xml description and screenshot

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 templates or Enterprise)
  • 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

Marketing

Build

All actions to be done on the release branch (git pull; git checkout -b release-x.x.x) from here:

  • Bump version in appinfo/info.xml (no version suffix)
  • Check php version dependency and minimum ownCloud version dependency in appinfo/info.xml
  • Bump "sonar.projectVersion=" in sonar-project.properties (no version suffix)
  • Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

  • git tag -s v${version}-rc.1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
  • Build and sign RC tarball from github tag v${version}-rc.1 (see handbook for how to build)
  • Check buildlog for security reports
  • Check github security tab dependabot reports
    • -> if critical or high entries are reported: open a release blocker issue.
  • 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
    • Watch out for untranslated strings when locale is de oder de_DE.
    • PHP 7.3 compatibility (HCLOUD_SERVER_IMAGE=debian-10 OC10_VERSION=10.11 oc10.sh ...)
    • => 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

@phil-davis phil-davis added this to Qualification in Releases via automation May 23, 2023
@jnweiger jnweiger moved this from Qualification to Dev done, RC needed in Releases Aug 31, 2023
@jnweiger
Copy link
Contributor

jnweiger commented Oct 5, 2023

@GeraldLeikam GeraldLeikam moved this from Dev done, RC needed to In QA in Releases Oct 9, 2023
@jnweiger
Copy link
Contributor

Changelog QA passed. the critical tokenizer error #331 is fixed. Some more errors around #287 exist, new issues opened. Not considered blockers.

@GeraldLeikam GeraldLeikam moved this from In QA to QA done in Releases Oct 30, 2023
@jnweiger jnweiger modified the milestones: qa, davitol-qa, QA Nov 2, 2023
@jnweiger jnweiger moved this from QA done to Release done 🎉 in Releases Nov 2, 2023
@phil-davis
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Releases
  
Release done 🎉
Development

Successfully merging a pull request may close this issue.

2 participants