Release 7.2.0

未关闭
#12,673 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp
领域
release

调研方向

This release checklist names the client repository, the release template at .github/release_template.md, CHANGELOG.md, and linked QA plans as references. Start by reading the checklist and checking the release template and changelog; completing it requires coordinating build, QA, documentation, publishing, and infrastructure steps across the release. Done when the checklist for version 7.2.0 is completed and the release is published.

由索引模型根据 Issue 内容生成。

描述

QA:team
Administration
  • QA: Update Test Plans
  • Update supported platforms
  • QA: Check the translations coming from transifex: https://github.com/owncloud/client/commits/ -> Filter based on a release branch/tag and search for [tx] updated client translations from transifex [skip ci]
  • DEV: Check for new OpenSSL version
  • DEV: Update dependencies
  • DEV: For a major release create X version branch
    • QA: In drone adjust the branch for nightly GUI tests @individual-it
  • QA: Communicate documentation changes
    • Inform documentation team about the start of testing phase (latest a week before the release!). They'll prepare a PR with respective doc version
    • Open issues in docs-client-desktop repo for already known doc-relevant items and mark them accordingly, e.g. backport to 2.X.x necessary
  • Decide if the prerelease stage will be public or internal
Copy for Each Build (Beta/RC)
  • DEV: Tag (Beta or RC) and build builds for theme 'ownCloud' and 'testpilotcloud'
  • QA: Smoke test @sarita110 @shribisha613
  • DEV: GitHub release
  • Beta/RC Communication
  • DEV: Prepare the update server for new version (AppImages included)
    • DEV: Provide 'testpilotcloud' on Beta update channel
QA
  • QA: Antivirus scan the first RC @sarita110 @shribisha613
  • QA: Upload linux gpg keys to key server
  • QA: Check Crash reporter: start 'owncloud --debug' on cmd line, system tray right click menu: 'Crash now - qt fatal' -> report window not empty, sending the report works
    1. Start owncloud --debug on cmd line
    2. System tray right-click menu: Crash now - qt fatal -> report window not empty, sending the report works
    • Windows @sarita110
    • macOS
    • AppImage (Linux) @shribisha613
  • Automated tests (for the first beta and the last RC):
  • Manual tests:
    • QA: Changelog test @PrajwolAmatya
    • QA: Regression test @Asmitapaudel @sarita110 @shribisha613
    • QA: Branded regression test
Prerequisites for final release
  • DEV: Create v7.2.0 release tag in client repo and everywhere else
  • DEV: bump VERSION.cmake in master to say X.(Y+1).Z unless already done.
Final Rebuild after QA Approval
  • QA: Inform documentation team that the tag for the final release will be set a day or at least half a day before (only for a major/minor release). They'll merge docs PR before that.
  • DEV: Create final release tag (e.g., v7.2.0)
  • DEV: Create builds for themes 'ownCloud' and 'testpilotcloud' for final release tag
  • DEV: Update version for future builds
  • QA: Check squish tests running successfully on drone for the final tag v7.2.0
  • QA: Create a new release issue for a branded release if needed Branded Client Release Template
Final Steps
  • QA: Smoke test
  • DEV: Publish the release in GitHub
  • QA: Update lines 4 and 5 of install docs with the final build number. Merge into master and backport to the respective branch
  • QA: Check that documentation offers the new version
  • DEV: Merge version branch into master
  • DEV: Update SBOM
Marketing and Communication
Infrastructure Check
  • QA/DEV: Update stable channel in the owncloud hosted auto updater
  • QA: Check the linux download pages whether the URLs are correct (e.g. contain stable, not testing)
  • QA: Ensure that the client release template is up to date
A Few Days After the Release

Bug Reports

主要语言
C++
星标
1.5k
派生
695
平均合并
8 天 7 小时
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

owncloud/client 的其他 Issue

查看 owncloud/client 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。