Skip to content

Ensure steady score increase between v3.0 and v3.1 #495

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
Closed
camillobruni opened this issue Feb 28, 2025 · 1 comment
Closed

Ensure steady score increase between v3.0 and v3.1 #495

camillobruni opened this issue Feb 28, 2025 · 1 comment
Assignees
@camillobruni
Labels
v3.1

Comments

@camillobruni
Copy link
Contributor

For HW developer / external folks it's nice if the score doesn't change too much between releases.
After merging all score-changing changes back to v3.1 we should do a thorough measurement round and potentially adjust the score calculation so we don't have a score decrease with the new version.
@camillobruni camillobruni self-assigned this Feb 28, 2025
@camillobruni
Copy link
Contributor Author

double checked and agreed that the 1-2% change is acceptable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@camillobruni camillobruni

Labels
v3.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@camillobruni