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

Mark ignored versions which are included into the latest release bounds as newest #1182

Closed
AMDmi3 opened this issue Oct 1, 2021 · 0 comments

Comments

@AMDmi3
Copy link
Member

AMDmi3 commented Oct 1, 2021

Additional idea to #920 and #801.

In a case when we have a latest version (say, 1.2.3) and a some ignored post-snapshots of it (say, 1.2.3.20210101) we may mark them as newest in additional classification pass, based on the fact that they are included in the latest release. This is just an idea which I don't plan to implement since gain from marking these snapshots as newest is doubtful - this improves repositories' statistics (higher percentage of newest versions), but fails to discourage snapshots and masks difference between official versions and snapshots, and between snapshots of different freshness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant