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

Optimize Changelog fetching #6171

Closed
Tracked by #14138
rarkins opened this issue May 8, 2020 · 0 comments
Closed
Tracked by #14138

Optimize Changelog fetching #6171

rarkins opened this issue May 8, 2020 · 0 comments
Assignees
Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:refactor Refactoring or improving of existing code

Comments

@rarkins
Copy link
Collaborator

rarkins commented May 8, 2020

Changelogs often get changes in the first hours after a release but it gets increasingly unlikely over time. It does not make sense for us to check/re-fetch release notes hourly when the release is weeks or months old, etc.

We should look into how we can use timestamps to intelligently increase the caching time of results. Timestamps could come potentially from both (a) the datasource, or (b) the changelogs.

@rarkins rarkins added ready priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:refactor Refactoring or improving of existing code labels May 8, 2020
@rarkins rarkins self-assigned this Jun 14, 2020
@rarkins rarkins removed the ready label Jun 18, 2020
@HonkingGoose HonkingGoose added the core:changelogs Related to changelogs/release notes fetching label Sep 1, 2021
@rarkins rarkins closed this as completed Jun 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core:changelogs Related to changelogs/release notes fetching priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:refactor Refactoring or improving of existing code
Projects
None yet
Development

No branches or pull requests

2 participants