Login or Register to Ask a Question and Join Our Community


Web Development

Automated creation of release notes

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Web Development Automated creation of release notes
# 1  
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?
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT BSD

checknotes

CHECKNOTES(1)						      General Commands Manual						     CHECKNOTES(1)

NAME

       checknotes - check for new notesfile articles

SYNOPSIS

       checknotes [ -qnvs ] [ -aname ]

DESCRIPTION

       Checknotes  reports  on	the existence of new notes.  The NFSEQ environment variable is read to determine the notesfiles to examine for new
       text.  Checknotes then looks at each of the notesfiles to determine if there are new notes.  The various flags specify the method of  noti-
       fication.  The flags are mutually exlusive.

       The -q option specifies a message ``There are new notes'' when such is the case.  No text is printed if there are no new notes.

       Specify -n to get a message ``There are no new notes'' if this is the case.  If there are new notes, no message is printed.

       With the -v option enabled, checknotes prints the name of each notesfile containing new notes.

       The -s option is silent; no output is produced.

       Regardless of the option, the program exits with 0 (TRUE) if new notes exist and with 1 (FALSE) if no new notes exist.

       The  -a	option	specifies a subsequencer.  This allows several people sharing the same signon to maintain their own sequencer files.  This
       switch does not allow users to forge other user's sequencer files.  Since the name is concatenated with the  user  name,  arbitrarily  long
       subsequencer  names  aren't  necessarily unique.  A good rule of thumb is to ensure the first 6 characters of any given user's subsequencer
       names are unique.

FILES

       /etc/passwd				    for the users name
       /etc/group				    for the users group(s)
       /usr/spool/notes 			    the default notesfile data base
       /usr/spool/notes/.sequencer/user 	    Sequencing timestamps for user.
       /usr/spool/notes/.sequencer/user:subsequencer
						    Sub-sequencing timestamps for user.

SEE ALSO

       notes(1),
       The Notesfile Reference Manual

AUTHORS

       Ray Essick (uiucdcs!essick, essick%uiuc@csnet-relay.arpa)
       Department of Computer Science
       University of Illinois at Urbana-Champaign
       Urbana, IL

       Rob Kolstad (kolstad@convex.UUCP)
       CONVEX Computer Corporation
       Richardson, TX

							      University of Illinois						     CHECKNOTES(1)