Skip to content

Build a release policy #1218

Open
Open
Build a release policy#1218
Labels
area/meta/workflowRelates to the contributor workflowkind/documentationRelates to documentationpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next releasetriage/acceptedThis issue is accepted
Milestone
0.11.0

Description

@sudoforge
sudoforge
opened on Aug 2, 2024

We should have a documented release policy, which provides a runbook for the process of creating a new release, as well as describes how commits are collected into releases.

Activity

  1. sudoforge
    added this to the 0.9.0 milestone on Aug 2, 2024
  2. sudoforge
    added
    kind/documentationRelates to documentation
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release
    triage/acceptedThis issue is accepted
    area/meta/workflowRelates to the contributor workflow
    on Aug 2, 2024
  3. sudoforge
    modified the milestones: 0.9.0, 0.8.1 on Aug 2, 2024
  4. sudoforge
    added
    lifecycle/active
    on Apr 1, 2025
  5. sudoforge
    modified the milestones: 0.8.1 (next), 0.8.2 on Apr 20, 2025
  6. sudoforge
    removed
    lifecycle/active
    on Apr 28, 2025
  7. sudoforge
    modified the milestones: 0.10.2, 0.11.0 on May 19, 2025
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

    area/meta/workflowRelates to the contributor workflowkind/documentationRelates to documentationpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next releasetriage/acceptedThis issue is accepted

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions