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

Cut a release for Flatpak, etc. #417

Closed
jacksongoode opened this issue May 13, 2023 · 6 comments
Closed

Cut a release for Flatpak, etc. #417

jacksongoode opened this issue May 13, 2023 · 6 comments

Comments

@jacksongoode
Copy link
Collaborator

jacksongoode commented May 13, 2023

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 @jpochyla

@TheEvilSkeleton
Copy link

I agree. Otherwise, if you think it's not production ready, then we could start with experimental releases.

@Insprill
Copy link
Collaborator

A major version > 0 indicates a stable application, which psst is not. If we switch to semantic versioning, we'll start at 0.1.0. I haven't used Flatpak before; does it not let us use a git hash for a version? If we are to switch to semantic versioning, I'd like to hear @jpochyla's thoughts.

@jpochyla
Copy link
Owner

Personally I'd prefer 0.1.0, yes.

@TheEvilSkeleton
Copy link

TheEvilSkeleton commented May 15, 2023

does it not let us use a git hash for a version?

Flatpak (the format) does, but Flathub (the store) prefers semantic versioning

@jacksongoode
Copy link
Collaborator Author

I'm good with 0.1.0 - I can close this issue and we can go ahead?

@TheEvilSkeleton
Copy link

You have my approval

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

4 participants