This repository was archived by the owner on Dec 10, 2024. It is now read-only.
Frequent releases without data changes #70
Labels
Comments
priv-kweihmann
changed the title
priv-kweihmann
added a commit
that referenced
this issue
Mar 16, 2023
if there are no relevant changes in the data, just push the new timestamp but do not release a new version Relates to #70 Signed-off-by: Konrad Weihmann <[email protected]>
priv-kweihmann
added a commit
that referenced
this issue
Mar 16, 2023
if there are no relevant changes in the data, just push the new timestamp but do not release a new version Relates to #70 Signed-off-by: Konrad Weihmann <[email protected]>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Sep 5, 2023
Note that the timestamp in the matrix does not necessarily reflect the date when the new matrix data was released, but when it was downloaded. See [1] in that context. [1]: priv-kweihmann/osadl-matrix#70 Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Sep 5, 2023
Note that the timestamp in the matrix does not necessarily reflect the date when the new matrix data was released, but when it was downloaded. See [1] in that context. [1]: priv-kweihmann/osadl-matrix#70 Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Nov 22, 2023
Note that the timestamp in the matrix does not necessarily reflect the date when the new matrix data was released, but when it was downloaded. See [1] in that context. [1]: priv-kweihmann/osadl-matrix#70 Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Nov 23, 2023
Note that the timestamp in the matrix does not necessarily reflect the date when the new matrix data was released, but when it was downloaded. See [1] in that context. [1]: priv-kweihmann/osadl-matrix#70 Signed-off-by: Sebastian Schuberth <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After the discussion happened in #29, upstream implemented a timestamp within the json that this library fetches regularly.
Due to reasons we do not know the timestamp of the file changes in the upstream source almost daily without any other data changes.
The situation is not ideal, as we have to do a lot of releases that do not add any value in terms of data, but just for the sake of delivering the latest upstream source.
The ticket is just to have some visibility on the issue.
The text was updated successfully, but these errors were encountered: