You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
if this should be added, i prefer the second approach.
first and foremost it looks cleaner, the heading always stay as expected and it doesn't mater how much you put in it. if it would be in a heading this gets sooner than later quite a mess and confusing.
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:
The text was updated successfully, but these errors were encountered: