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
When the user searches for packages that he maintains that are updated elsewhere he gets a potentially long list of packages. For example, yesterday it was 72, today it became 74. 2 packages were likely added to the list. But what these packages are? There is no obvious way to determine this other than by saving snapshots and comparing them.
Once some Newest version appears in the list, its date of first discovery is also relevant.
Suggestion:
Add the "Newest Discovery Date" field, and allow the user to sort by it.
This way the user would be able to see what packages were updated last, which is very relevant.
Ability to determine the latest changes is especially important because Repology produces false positives and the list of outdated packages could be large because of this.
The text was updated successfully, but these errors were encountered:
Problem:
When the user searches for packages that he maintains that are updated elsewhere he gets a potentially long list of packages. For example, yesterday it was 72, today it became 74. 2 packages were likely added to the list. But what these packages are? There is no obvious way to determine this other than by saving snapshots and comparing them.
Once some
Newest
version appears in the list, its date of first discovery is also relevant.Suggestion:
Add the "Newest Discovery Date" field, and allow the user to sort by it.
This way the user would be able to see what packages were updated last, which is very relevant.
Ability to determine the latest changes is especially important because Repology produces false positives and the list of outdated packages could be large because of this.
The text was updated successfully, but these errors were encountered: