Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

imrpove release process #367

Open
pmeier opened this issue Mar 18, 2024 · 1 comment
Open

imrpove release process #367

pmeier opened this issue Mar 18, 2024 · 1 comment
Assignees
Labels
area: documentation 📖 Improvements or additions to documentation
Milestone

Comments

@pmeier
Copy link
Member

pmeier commented Mar 18, 2024

Currently, I'm manually creating and publishing releases. This has two downsides:

  1. Releasing involves quite a few steps. Doing them manually opens up the window for mistakes.
  2. All the knowledge on how to release currently is in my head and not documented anywhere else. If I'm unable to do a release for some reason, others will have a hard time replicating my process.

To overcome this, I propose two things:

  1. Automate as much as possible through GitHub Actions.
  2. Write up the release process in the documentation so everyone with the right permissions can do it.
@pmeier pmeier added the area: documentation 📖 Improvements or additions to documentation label Mar 18, 2024
@pmeier pmeier added this to the 0.3.0 milestone Mar 18, 2024
@pmeier pmeier self-assigned this Mar 18, 2024
@arjxn-py
Copy link
Contributor

arjxn-py commented Jun 3, 2024

A build workflow has already been created for both ragna & ragna-base in #405 which can further be extended to publish the built wheels plus the same can be documented as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation 📖 Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants