Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Implement asset version history #10

Closed
Calinou opened this issue Oct 2, 2019 · 2 comments
Closed

Implement asset version history #10

Calinou opened this issue Oct 2, 2019 · 2 comments

Comments

@Calinou
Copy link
Owner

Calinou commented Oct 2, 2019

This can be used by asset uploaders to give more information to users.

Multiple versions could be stored per asset, each with a version identifier, a date and some release notes (with possible Markdown formatting).

We could make old versions downloadable manually via the Web interface, but the editor integration would likely only provide the latest version for simplicity's sake.

@Calinou
Copy link
Owner Author

Calinou commented Nov 13, 2019

This is now implemented on the backend, but old versions remain to be displayed on the Web frontend.

I'm not sure about release notes though – maybe letting people link to a CHANGELOG.md file is sufficient. In general, I'm in favor of moving data to the repository so it can be easily viewed by anyone (including those finding the asset directly on GitHub or similar).

@Calinou Calinou self-assigned this Nov 19, 2019
@Calinou
Copy link
Owner Author

Calinou commented Jan 17, 2020

The version history is now displayed on the Web frontend and API, closing.

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

No branches or pull requests

1 participant