Skip to content

Decision post on why to do continuous delivery #105

@lwjohnst86

Description

@lwjohnst86

Include the benefits of using this approach even for non-software projects:

  • Less time spent/dedicated to "editorial" phases
  • Including specific "phases" of development before publication, like drafting and reviewing. If all changes are treated as additions to a finished working product, then there are no phases
  • Since the assumption is now "any change goes live", it makes it easier to keep things updated, since making a PR that immediately goes into "delivered/deployed/published" status and you don't need to have the overhead of coordinating a "review/edit phase"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions