79342bcd8d
Previously, detecting unsaved changes relied on whether there are any changes that happened in the editing view. This would mean, that after using "Save as" unsaved changes were still assumed. |
||
|---|---|---|
| .. | ||
| 47.0 | ||
| 47.1 | ||
| 47.2 | ||
| 47.4 | ||
| 47.alpha | ||
| 47.beta | ||
| 47.beta.1 | ||
| 48.0 | ||
| 48.1 | ||
| 48.alpha | ||
| 48.beta | ||
| 48.rc | ||
| 49.0 | ||
| 49.1 | ||
| 49.2 | ||
| 49.alpha | ||
| 49.beta | ||
| 49.rc | ||
| 50.0 | ||
| 50.alpha | ||
| 50.beta | ||
| 50.rc | ||
| 51.alpha | ||
| 51.beta | ||
| 51.rc | ||
| previous | ||
| README.md | ||
NEWS
The NEWS file is automatically generated from this directory.
Please add a file for each changelog entry to the subolder corresponding to the version. Usually, this will be the latest version that has a folder. The files begin with a category prefix like changed- or fixed-. The prefixes follow the categories from keepachangelog.com.
The NEWS files needs to be generated via ./build-aux/generate-news.py and commited before releases.