Is it possible to reconcile headline driven development with the structure of a keep-a-changelog changelog, or are they at cross purposes?
For example:
# Changelog
## [Unreleased] - Netscape 6 and IE 6 support
### Added
* Support for Netscape 6
### Changed
* Deprecated support for Opera 3
## [1.0.0] - 2001-01-01 - Website released!
### Added
* A scrolling marquee, to keep visitors occupied.
* An under construction sign, so visitors know there is more to come
or perhaps the headline could live between the heading and the detail sections:
# Changelog
## [1.0.0] - 2001-01-01
Website released!
### Added
* A scrolling marquee, to keep visitors occupied.
* An under construction sign, so visitors know there is more to come
Is it possible to reconcile headline driven development with the structure of a keep-a-changelog changelog, or are they at cross purposes?
For example:
or perhaps the headline could live between the heading and the detail sections: