Skip to content

release progress guide #32

@setoru

Description

@setoru

Formalize release management process in RELEASE.md to ensure consistent and reliable software delivery.

  • main branch and release branch definition
  • release process, including release note, release blog, release CI(blocking CI)
  • patch process: cherry-pick requirements and scope(CVE and critical issues by default)
  • general release plan, such as a release per year or every 3 months

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions