Making a New DAPS Release

Preparing a Release

In order to create a release, do the following:

1. Start a new release branch and replace RELEASE with the number you would like to create:

$ git flow release start RELEASE

1. Adapt version number in `configure.ac`.
1. Run `autogen.sh`.
1. Adapt version number in `packaging/daps.spec`..
1. Write a meaningful ChangeLog entry listing all changes and bugfixes
1. Check the readme files for occurences of the old version number
1. Commit your changes
1. Finish the release branch with:

$ git flow release finish RELEASE

   Add the following messages:
   - the log message for the `develop` branch
   - the message for the tag
   - the log message for the `master` branch

1. Update the [GitHub Pages](https://github.com/openSUSE/daps/wiki/Updating-GitHub-Pages)
1. Update the ChangeLog and readme.install on [SourceForge](https://sourceforge.net/projects/daps/files/)
1. Post an announcement at the [Forum](https://sourceforge.net/p/daps/discussion/)

## Creating a Release on OBS
1. If you haven't done yet, install the package `osc` and `build` and checkout the `Documentation:Tools` repo:

$ osc checkout Documentation:Tools daps

1. Change to the OBS working copy.
1. Run `daps-fetch-source-git` to get the latest changes from GitHub.
1. Run `osc vc` and add your changelog.
1. Rebuild the package, fix any errors, and commit to OBS.