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.

Sign up for GitHub

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

Jump to bottom

Communicate release process #823

Open
Farhad-Shabani opened this issue Aug 9, 2023 · 0 comments
Open

Communicate release process #823

Farhad-Shabani opened this issue Aug 9, 2023 · 0 comments
Labels
S: docs Scope: improvements or additions to documentation

Comments

@Farhad-Shabani
Copy link
Member

Farhad-Shabani commented Aug 9, 2023 •
edited

Background

Regarding releases, we have a step-by-step guide that assists developers in cutting a release. However, there is a gap in how we convey our release process to the wider community. Prior to our first stable release, we should:

  • Explain our versioning system and any deviations.
  • Details about our release cycle
  • A version dependency table that corresponds versions with compatible Rust and key dependencies like ibc-proto-rs and tendermint-rs
  • Perhaps a stable release policy
@Farhad-Shabani Farhad-Shabani added the S: docs Scope: improvements or additions to documentation label Aug 9, 2023
@Farhad-Shabani Farhad-Shabani changed the title Enhance release process communication Communicate release process Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S: docs Scope: improvements or additions to documentation
Projects
ibc-rs
Status: 📥 To Do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Farhad-Shabani