Sponsored Content
Top Forums Web Development Automated creation of release notes Post 302879492 by figaro on Thursday 12th of December 2013 04:47:16 PM
Old 12-12-2013
Automated creation of release notes

Does anyone have experience in an automated creation of release notes? We already have automated nightly builds and regression tests of C++ and Python software, but we do not yet create our releases automatically.
If releases are either bug fix releases or feature releases (containing both bug fixes and enhancements), then the former would be the easiest to do: create a list of all the issues resolved between the previous release date and the current date.
For feature releases it is a little more complicated, because we do not have a well structured repository of feature requests yet.
So are there any suggested best practices that will help us create release notes automatically for in particular feature releases?
 
ARCHPATH(1)                                                   General Commands Manual                                                  ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN Debian Utilities ARCHPATH(1)
All times are GMT -4. The time now is 01:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy