Maesh is an open source project, and your feedback and contributions are needed and always welcome.
Non trivial changes should be discussed with the project maintainers by opening a Feature Request clearly explaining rationale, background and possible implementation ideas. Feel free to provide code in such discussions.
Once the proposal is approved, a Pull Request can be opened. If you want to provide early visibility to reviewers, create a Draft Pull Request.
Maesh follows the semver sheme when releasing new versions.
Therefore, all PR's (except fixing a bug in a specific version) should be made against the
master branch. If you're attempting to fix a bug in an already released version, please use the correct branch of that release (e.g.
v1.1). All bug-fixes made to a specific branch will be backported to master, prior to releasing a new (major / minor) version. Patch releases will be made out of the version branch.
In order to release a new version of Maesh, the following steps have to be done:
- Create a Prepare release PR updating the chart version and app version to upcoming release
- Prepare a list of release notes for the #maesh
- Merge Prepare release PR
- Create and push a tag on the release commit
- Create a new release branch (v1.x) on upstream to allow versioned docs to be built