Project

General

Profile

Feature #8689

Consider building the changelog from changes files provided by the merged branches

Added by intrigeri over 4 years ago. Updated 18 days ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
-
Category:
-
Target version:
-
Start date:
01/13/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

... just like they do it for Tor. This would make the release process shorter by pushing to branch submitters the responsibility to write good changelog entries. It would also be needed to go further on the continuous integration path (releasing stuff automatically).

If we go this way, we could even request two different pieces of text:

  • a changelog snippet
  • a release notes snippet, if the changes warrant being mentioned there

=> our doc writers could review and improve the release notes incrementally during a dev cycle, instead of doing it in one go at release time (which is a blocking synchronization point right now).

The relationship between this and the process of writing the release notes was discussed on https://mailman.boum.org/pipermail/tails-project/2015-February/000118.html. One should re-read this discussion before starting work on this ticket, but IIRC the summary is that the release notes draft, once automatically assembled from the snippets at RC time, can be published on a blueprint that anyone can help improve (even if they're not at ease with Git).

History

#1 Updated by sajolida over 4 years ago

If we go this way, then the section "Documentation is not optional" should be adapted to make explain the additional requirements.

#2 Updated by sajolida about 4 years ago

  • Assignee set to bertagaz

#3 Updated by sajolida about 4 years ago

  • Target version changed from Sustainability_M1 to 2016

#4 Updated by anonym over 3 years ago

If implemented, for bugfixes we should mandate that the changelog entry includes "bugfix on $version_that_introduced_the_bug" when relevant.

#5 Updated by intrigeri over 3 years ago

https://github.com/openstack/reno provides a workflow and tools to handle that.

#6 Updated by Dr_Whax about 3 years ago

  • Assignee deleted (bertagaz)
  • Priority changed from Normal to Elevated
  • Target version deleted (2016)

#7 Updated by intrigeri almost 3 years ago

  • Description updated (diff)

#8 Updated by intrigeri 18 days ago

  • Category deleted (Continuous Integration)

Also available in: Atom PDF