Skip to content

Release process #3

@braydend

Description

@braydend

Why?

I need to define a release process that will allow the repo to be easily managed over time. A concrete release process will also ease the developer experience of anyone that ends up consuming this package.

Ideas

  • Commitizen style commit helper. This will allow for automatic changelogs and releases.
  • Robust CI. Linting and test checking on build before merging to the main branch will increase code quality and reliability.
  • License. I need to find what kind of license I want to apply to this software

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions