Remove release announcement from definition of done

[korthout]

Description

Removes the release announcement task from the Definition of Done that exists in the GitHub pull request template.

The Zeebe team used to be responsible for writing the release blog post. To help remember what is part of which release, the Blog Post folder on Google Drive could be used to update the release announcement. Since the team is no longer responsible for this, we see no value in keeping this document up to date.

Related issues

NA

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

• The changes are backwards compatibility with previous versions
• If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

• There are unit/integration tests that verify all acceptance criterias of the issue
• New tests are written to ensure backwards compatibility with further versions
• The behavior is tested manually
• The change has been verified by a QA run
• The impact of the changes is verified by a benchmark

Documentation:

• The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
• New content is added to the release announcement
• If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

[github-actions]

Test Results

   949 files  ±    0     949 suites  ±0   1h 43m 19s ⏱️ + 2m 37s
7 602 tests  - 100  7 595 ✔️  - 100  7 💤 ±0  0 ❌ ±0 
7 800 runs   - 100  7 791 ✔️  - 100  9 💤 ±0  0 ❌ ±0 

Results for commit f8d44d7. ± Comparison against base commit dfae49f.

[saig0]

@korthout 👍