Build automation – automatically generate “new features in this release” reading

We all know – this is the reading content, which lists the changes brought about by each new version of our favorite software. Whenever it is bundled as a file (Changes.txt, CHANGES , WhatsNew.txt, etc.) or when presented in the installer, this is usually the first thing we read before installation/update.

In the current project, we have a Changelog. txt file, it will be updated manually every time there is a significant change. However, this often leads to “I forgot to update the change log”. So I am looking for an automated method.

I am thinking of a script, which Extract changes from our commit message (using conventions) and generate files. For example, commit message

Updated json-glib to 0.7.6

< p>[changes]

- Fix crash on Windows

- Fix issues with facebook contacts with very large UIDs.

The following changes will be generated .txt

Version 1.9.18 (03/10/2010)

  • Fix crash on Windows
  • Fix issues with facebook contacts with very large UIDs.

Does anyone know a better solution/tool, or would I write it myself?

Thank you!

You can automatically generate it from the description in the bug tracking system to find the tags in this version Is a fixed error. If you distinguish the error from the feature request, then you can also mark it.

I use MantisBT to handle the error, which will automatically generate an out-of-the-box The change log.

We all know – this is what we read, listing the changes brought about by each new version of our favorite software. Whenever it’s When files are bundled (Changes.txt, CHANGES, WhatsNew.txt, etc.) or presented in the installer, this is usually the first thing we read before installation/update.

In the current In the project, we have a Changelog.txt file that will be manually updated every time a significant change occurs. However, this often leads to “I forgot to update the change log”. So I am looking for an automated method.

I am thinking of a script that extracts changes from our commit message (using conventions) and generates a file. For example, the commit message

Updated json-glib to 0.7.6

[changes]

- Fix crash on Windows

- Fix issues with facebook contacts with very large UIDs.

The following Changes.txt will be generated

Version 1.9.18 (03/10/2010)

  • Fix crash on Windows
  • Fix issues with facebook contacts with very large UIDs.

Does anyone know a better solution/tool, or I will myself write?

Thank you!

You can automatically generate it from the description in the bug tracking system to find bugs in this version that are marked as fixed. If you combine bugs with features The request is distinguished, then you can also mark it.

I use MantisBT to handle errors, which will automatically generate an out-of-the-box change log.

Leave a Comment

Your email address will not be published.