-
Notifications
You must be signed in to change notification settings - Fork 103
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
Update version stability section of quality declaration for 1.0. #256
Conversation
Signed-off-by: Steven! Ragnarök <steven@nuclearsandwich.com>
coverage is not yet ready. It's QD 3. |
Signed-off-by: Steven! Ragnarök <steven@nuclearsandwich.com>
Bumped to QL3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
README.md needs to be updated too
Signed-off-by: Steven! Ragnarök <steven@nuclearsandwich.com>
I think it's really unfortunate we duplicate this info. What do we think of just linking to the quality declaration? Yeah it's "one more click" but it's one less way to be wrong. |
We have discussed we should have some sort of badges similar to the ones shown with CI results, but for the time being is yet too be implemented. In fact I just realized with this PR you should update too the table at the end of the QD with a check for version stability. |
🤦 |
Signed-off-by: Steven! Ragnarök <steven@nuclearsandwich.com>
1.0 for this package was bumped in 5977357 so this updates the quality declaration.
It looks to me like this might make the package level 2 or level 3. I'd appreciate a comment on that front from someone whose got more familiarity with what's part of each quality level.