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

Pin issues to specific Iroha versions #489

Closed
nxsaken opened this issue May 20, 2024 · 3 comments
Closed

Pin issues to specific Iroha versions #489

nxsaken opened this issue May 20, 2024 · 3 comments
Assignees
Labels
A-important High-impact, important change L-versioning Issues relating to versioning M-meta Issues/PRs on the documentation itself (presentation, localization, navigation, etc.)
Milestone

Comments

@nxsaken
Copy link
Contributor

nxsaken commented May 20, 2024

Currently, it's unclear which version of Iroha is targeted by an issue. This may cause (and have caused) the issue's Definition of Done to change on a new release – especially since Iroha is evolving quicker than the documentation can keep up.

To remedy this, we should be more specific about what Iroha version should be used as the source of truth. This way, even if a release happens, the goalpost for the issue stays the same. A separate issue targeting the new version can be opened instead, if needed. This will also help us support multiple versions of the documentation.

@nxsaken nxsaken added the M-meta Issues/PRs on the documentation itself (presentation, localization, navigation, etc.) label May 20, 2024
@nxsaken nxsaken self-assigned this May 20, 2024
@nxsaken nxsaken added L-versioning Issues relating to versioning and removed iroha2 labels May 20, 2024
@mversic
Copy link
Contributor

mversic commented May 21, 2024

the person who opens the issue, should write how to reproduce it. This means to write the version of iroha which was used

@Mingela
Copy link

Mingela commented May 21, 2024

We could have a quick sorting with introducing major version labels (e.g. LTS and stable as of now)

@nxsaken nxsaken added this to the 2.0.0-rc.1.0 milestone May 24, 2024
@nxsaken nxsaken added the A-important High-impact, important change label May 24, 2024
@outoftardis
Copy link
Contributor

we have done this, we have labels now, I don't think this issues should remain open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-important High-impact, important change L-versioning Issues relating to versioning M-meta Issues/PRs on the documentation itself (presentation, localization, navigation, etc.)
Projects
None yet
Development

No branches or pull requests

4 participants