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

Creation of Release Versions #64

Open
rlaphoenix opened this issue Apr 14, 2022 · 0 comments
Open

Creation of Release Versions #64

rlaphoenix opened this issue Apr 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@rlaphoenix
Copy link
Collaborator

rlaphoenix commented Apr 14, 2022

📝 Provide a description of the new feature

Currently, users have no idea what versions are supported or how up-to-date the repository is relative to Spicetify and Spotify updates.

We could start making release versions of the project instead, following SemVer where each major update represents support for the next Spotify major update.

E.g., Assuming we start the first release at 1.0.0 indicating support for what we have now, 1.80.x. Then a 2.1.2 release would indicate support for Spotify 1.81.x and has 1 feature update, after which has also had 2 fixes.

We could also go the route of just releasing starting with the major version, e.g., 80.0.0. Therefore 81.1.2 would then indicate the same as before. This route is more readable but indicates that the project has gone through more updates than it actually has.

➕ Additional Information

I cannot say versioned releases for Spicetify themes are common, but it has been done before by @JulianMaille. You can see some examples of the route he has taken here:

As for documentation of releases, we can use the Keep a Changelog spec to keep it tidy, readable, and to the point.

@rlaphoenix rlaphoenix added the enhancement New feature or request label Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant