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

Rethink versioning #253

Open
nikitaDanilenko opened this issue Feb 26, 2024 · 0 comments
Open

Rethink versioning #253

nikitaDanilenko opened this issue Feb 26, 2024 · 0 comments

Comments

@nikitaDanilenko
Copy link
Owner

In its current state the versioning actually has three different versions: the project, the back end, and the front end. However, the project's version is redundant, and misleading, because it may be very different from both back end and front end. A better approach is to use two distinct versions for back end, and front end, and possibly accomodate the complement version in both, i.e. tags like v1.2.3-2.1.4 which denote how which versions are compatible with which complement version.

The concept seems poorly thought through now - rethink it, as the title suggests!

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

No branches or pull requests

1 participant