You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our release process is quite outdated, created couple of years ago. It would be good to update it with the most up-to-date developments in Charon.
🛠️ Proposed solution
We have a design doc where all the steps for a release are outlined, but it's more than 2 years old, pre-v1. It would be better to have a new updated doc that also encompasses the steps for minor and patch releases.
Second improvement of our release process would be to have template for our release notes. Currently it's more or less freestyle of how we structure them, but it will be easier for us and the users if there is some systematic structure.
What will speed up a lot the process is having automated Kurtosis testing for tagged versions. Currently we are working on deploying those tests on k8s in order to streamline multiple deployments. Once we are comfortable with this, it would be relatively easy to plug that into the pipelines.
The text was updated successfully, but these errors were encountered:
🎯 Problem to be solved
Currently our release process is quite outdated, created couple of years ago. It would be good to update it with the most up-to-date developments in Charon.
🛠️ Proposed solution
The text was updated successfully, but these errors were encountered: