summaryrefslogtreecommitdiff
path: root/changelog.txt
Commit message (Collapse)AuthorAge
* Bump to v0.5.2v0.5.2Matthew Heon2018-05-11
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.5.1v0.5.1Matthew Heon2018-05-04
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.4.4v0.4.4Matthew Heon2018-04-27
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.4.3v0.4.3Matthew Heon2018-04-20
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.4.2v0.4.2Matthew Heon2018-04-13
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.4.1v0.4.1Matthew Heon2018-04-05
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump to v0.3.5v0.3.5Matthew Heon2018-03-29
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Bump version to v0.3.4v0.3.4Matthew Heon2018-03-23
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Makefile: add changelog targetValentin Rothberg2018-03-21
Maintaining a changelog for each new version or release of Podman helps users to quickly skim for new changes. Add a `make changelog` target to facilitate creating a new log. There are two env variables to control the base and target commit for the new log. The output gets prepended to the changelog.txt file, which is a textfile in following format: - Changelog for $(CHANGELOG_TARGET) (ISO-8601 DATE): * Commit subject * Commit subject... Notice that the list of commit subjects excludes merge commits, and can be manually modified after generation if needed. `CHANGELOG_BASE=v0.3.2 CHANGELOG_TARGET=v0.3.3 make changelog` would generate the following shortened output to the changelog.txt file: Changelog for v0.3.3 (2018-03-17): * Bump to v0.3.3 * Fix build after c/image changes * Update containers/image * Fix E2E tests * Address review comments * Fix E2E tests * Add restart to main podman manpage * Add podman restart to podman bash completions and commands Signed-off-by: Valentin Rothberg <vrothberg@suse.com>