Skip to content

Add release policy #332

@qkrybin

Description

@qkrybin

Checklist

  • New Feature for the SVC/Plugin
  • New Feature for CI/CD
  • Enhancement on Vatz
  • Others(etc. e.g, documentation,...)

Please describe, what it's about or related Problem with

  1. it's hard to track feature changes and bug fixes.
  2. We don't have a policy about releasing and tracking those changes.

Describe the output that you are expecting for above

How about adding a release policy about tagging, testing, double-checking, and getting approval from opensource contributors for further releases?

Describe alternatives you've considered

add a changelog file to record history before we set the policy.

Additional context

Add any other context or screenshots about the feature request here.

Metadata

Metadata

Labels

VatzProject Namearea:projectAnything that related to Vatz project managetype:documentationAnything related to Vatz documentation with *.mdtype:feature-requestIf there anyone has to raise a hand to request new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions