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

Use Semantic Versioning #41

Open
AlexanderBabel opened this issue Feb 8, 2022 · 2 comments · May be fixed by #48
Open

Use Semantic Versioning #41

AlexanderBabel opened this issue Feb 8, 2022 · 2 comments · May be fixed by #48
Assignees

Comments

@AlexanderBabel
Copy link

Hey @lus,

first of all thank you for your work on pasty. I really like the project, the UI and the functionality.

But I would really appreciate if you could implement some kind of release management or tagging for different versions of pasty.
There are a few systems out there, like semantic-release (using conventional commits), that can help you with that. Here is also an example project where semantic release is used.

If you need some help with that, I am happy to support you.

@lus
Copy link
Owner

lus commented Feb 22, 2022

Hello!

Thank you for bringing this up.
I already thought about using semantic versioning but ultimately decided against it because I like the simplicity of using the commit hash as the version identifier.
I agree that semantic versioning makes sense and is very useful in many cases but I do not really see the advantage it would give to this specific project.
I think it would help if you could lay out why the current solution bothers you in particular so I can think about it.

@lus lus self-assigned this Feb 22, 2022
@lus
Copy link
Owner

lus commented Aug 22, 2022

Update: I thought a bit about this and I came to the conclusion to use Semantic Versioning from now on.

@lus lus changed the title Release Management Use Semantic Versioning Aug 22, 2022
@lus lus linked a pull request Aug 22, 2022 that will close this issue
11 tasks
@lus lus linked a pull request Aug 29, 2022 that will close this issue
11 tasks
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

Successfully merging a pull request may close this issue.

2 participants