9097b38f80
The existing behavior was to select issues closed between two tag dates. This is error prone since issues may be closed after the fact, and there may be multiple releases being worked at the same time and it is impossible to tell which release an issue was closed for. This switches to selecting issues by matching their milestone name against the git tag. Since github does not support assigning multiple assignments, their will likely need to be some manual issue additions to the release notes when an issue is targeted to multiple releases e.g. v2.0.1 and v2.1. This also moves to only triggering github release creation on non-pre-release semver tags, to avoid cluttering the release list. Change-Id: I99824020789323f8a1db418c73acef57ebb86022 Signed-off-by: Sean Eagan <seaneagan1@gmail.com>
Airshipctl
Airshipctl is a command-line interface that enables users to manage declarative infrastructure and software.
Airshipctl aims to provide a seamless experience for operators wishing to leverage the best open source options such as the Cluster API, Metal Kubed, Kustomize, and kubeadm by providing a straight forward and easily approachable interface.
This project is the heart of our effort to produce Airship 2.0, which has three main evolutions from Airship 1.0:
- Expand our use of entrenched upstream projects.
- Embrace Kubernetes Custom Resource Definitions (CRD) – everything becomes an object in Kubernetes.
- Make the Airship control plane ephemeral.
To learn more about the Airship 2.0 evolution, reference the Airship blog series.
Contributing
Airshipctl is under active development and welcomes new developers! Please read our developer guide to begin contributing.
We also encourage new contributors and operators alike to join us in our Slack workspace and subscribe to our mailing lists.
You can learn more about Airship on the Airship wiki.