Skip to content

headline driven development #616

Open

Description

@lsh-0

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

Activity

  1. DJCrashdummy commented on Nov 6, 2024

    @DJCrashdummy

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions