-
Notifications
You must be signed in to change notification settings - Fork 215
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
Cut a release for Flatpak, etc. #417
Comments
I agree. Otherwise, if you think it's not production ready, then we could start with experimental releases. |
A major version > 0 indicates a stable application, which psst is not. If we switch to semantic versioning, we'll start at |
Personally I'd prefer |
Flatpak (the format) does, but Flathub (the store) prefers semantic versioning |
I'm good with 0.1.0 - I can close this issue and we can go ahead? |
You have my approval |
In order for us to publish to Flathub #141 we need a real semantically versioned release, something that should have been tackled a while ago 😆.
My gut says we just start with
1.0.0
and increment the patch number from there? Maybe it would be good to have an action to do this automatically. @Insprill @TheEvilSkeleton @jpochylaThe text was updated successfully, but these errors were encountered: