JIRA: Balch - 7.3.0

Prerequisites

• DEV: Create stable branch
  • Create a stable-7.3 branch based on current master
• Finish release candidate phase
  • DEV: Prepare release-7.3.0-rc.1:
    • DEV: Branch off stable-7.3 branch
    • DEV: Move all changelog items from unreleased to 7.3.0-rc.1_2025-10-02
    • DEV: Bump ocis version in ocis-pkg/version/version.go
    • DEV: Bump ocis version in sonar-project.properties
    • DEV: Run a translation sync make l10n-pull
    • Create PR with [full-ci][k6-test] against stable-7.3 - [full-ci][k6-test] Release Balch 7.3.0-rc.1 #11711
    • Get PR approved. DO NOT MERGE YET
    • Wait for pipeline to be green
    • Create tag: git tag -s v7.3.0-rc.1 -m "Release 7.3.0-rc.1"
    • Push tag: git push origin v7.3.0-rc.1
    • Watch the PR to see pipeline succeed (can be restarted)
    • DEV: Generate Changelog: make changelog CHANGELOG_VERSION=7.3.0-rc.1
    • Merge PR
  • Sync with DevOps and Product - repeat process with rc.2,rc.3,... until all issues are fixed

QA Phase

• QA: Confirmatory testing (See changelogs)
  • ocis -> [QA] Confirmatory testing for Balch - 7.3.0 #11719 @Ashim-Stha
  • web -> [QA] Confirmatory testing for Web 12.1.0 web#13163 @anon-pradip
• QA: Compatibility testing
  • [QA] Compatibility testing for Balch - 7.3.0 QA#901 @anon-pradip
  • [QA] Compatibility testing for 7.1.4 to Balch - 7.3.0 QA#907 @anon-pradip
• Performance testing:
  • k6 Load performance tests for Balch - 7.3.0 - [QA] Performance testing for Balch - 7.3.0 QA#902 @deyankiteworks
  • k6 Specific load performance tests @deyankiteworks
• [QA] E2E with different deployment QA#903 @nirajacharya2
• QA: smoke testing
  • [QA] Smoke testing for Balch - 7.3.0 QA#904 @nirajacharya2
  • [QA] Text editor tests for Balch - 7.3.0 QA#905 @nabim777
  • [QA] Web office test for Balch - 7.3.0 QA#906 @Salipa-Gurung
• [QA] Check translations in German language for Balch - 7.3.0 #11725

Bug Reports

• Cli to delete personal spaces does not work #11724
• [QA] Check translations in German language for Balch - 7.3.0 #11725

Postponed issues

• Secure file can be open in onlyoffice #9664
• Refreshing a deleted public link for a file stuck at infinite loading state web#13174

After QA Phase

• Create release branch for 7.3.0
  • Branch off stable-7.3 branch
  • Move all changelog items from 7.3.0-rc.* to 7.3.0_2025-10-10
  • Bump ocis version in ocis-pkg/version/version.go
  • Bump ocis version in sonar-project.properties
  • Create PR with [full-ci][k6-test] against stable-7.3
  • Get PR approved. DO NOT MERGE YET
  • Wait for pipeline to be green
• Get release signoff (confluence)
  • Find someone who wants the release more desperately than you and tell that person to do it OR
  • Get appropriate people to sign release signoff document (not recommended)
• Release 7.3.0 ocis version
  • Create tag: git tag -s v7.3.0 -m "Release 7.3.0"
  • Push tag: git push origin v7.3.0
  • Watch the PR to see pipeline succeed (can be restarted)
  • Merge PR
  • Announce the release in Teams channel for oCIS

Post-release communication

• Create other stable branches, cronjobs and clean up
  • Backport release to master branch
  • Create a docs-stable branch
    • Create orphan branch: git checkout --orphan docs-stable-7.3
    • Initial commit: git commit --allow-empty -m "initial commit
    • Push git push
  • Adjust .drone.star file to write to docs-stable-7.3
    • Find target_branch value in the docs section and change it to docs-stable-7.3
    • Example: https://github.com/owncloud/ocis/blame/56f7645f0b11c9112e15ce46f6effd2fea01d6be/.drone.star#L2249
  • Add stable-7.3 to the nightly cron jobs in drone (Settings -> Cron Jobs)
  • For the docs-stable-7.3 branch to be ready the nightly cronjob needs to run. If needed this can be manually started with: drone cron exec owncloud/ocis nightly-7-3