Release customgroups 0.8.0

DeepDiver1975 commented 11 months ago

Using issue template from /home/testy/src/github/owncloud/QA/tools/release/templates/server_app_release_template.md

0.8.0 is to be bundled with core 10.13.3

[ ] 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

[x] Create QA Milestone and set the description to $version
[x] Move tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
[x] Create release branch with the format "release-$version"
[x] Create "$version Testplan" (QA templates or Enterprise)-> #615
[x] copy new/reopened issues from the previous release ticket as 'Issues to review' below.
[x] check if Non-normal Release Process applies, and adapt this checklist.

[ ] Changes in the docs needed? If so create issue in https://github.com/owncloud/docs-server/issues/new .

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

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

[x] git tag -s v${version}-rc.1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
[x] 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

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

[x] Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
[x] Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
[x] Rename QA milestone to $version and close the milestone
[x] Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
[x] Ensure release template is up to date
[x] Ensure the testplan template (community or enterprise) is up to date
[x] Close the testplan issue

jnweiger commented 11 months ago

jnweiger commented 10 months ago

Issues seen while testing

GeraldLeikam commented 10 months ago

close after release