Bug #17577

Release process: document (changelog) merging

Added by CyrilBrulebois 2020-04-01 04:00:47 . Updated 2020-04-01 04:00:47 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

As agreed among RMs, it would be great to tell the RM of the day how to proceed with merging branches in git; specifically which changelog (dummy) entries to keep in various cases. This would slightly reduce our having to rely on “best judgement”, and/or reduce the need for writing changelog entries intended to convince oneself (see commit:2c3afc8cce4f93383236606d02bcf04536e5a7ca).

Subtasks

Related issues

Related to Tails - Bug #17361: Streamline our release process Confirmed

History

#1 Updated by intrigeri 2020-04-01 07:33:26

  • related to Bug #17361: Streamline our release process added