You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: