Skip to content

ceo cycle = okr + version release #3

@crrow

Description

@crrow

Context

Each CEO work cycle should produce a version release.
BOSS reviews the released version, not intermediate state.

Design

  • CEO finishes cycle then commit, tag, push
  • BOSS daemon triggers on new tag (not state change)
  • BOSS reviews the diff since last tag

Acceptance

  • CEO cycle ends with git tag + push
  • BOSS daemon watches for new tags
  • BOSS review references specific version

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactorCode restructuring

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions