Release 7.2.0

オープン
#12,673 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間
マージ済み PR(30日)
6

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

owncloud/client のほかの issue

owncloud/client の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。