Current situation with snap is that each time we push into master a snap build is triggered in snapcraft which publishes to the edge channel. These are then tested and promoted to beta inside snapcraft once we're happy with the feature developed.
Once testing is complete we promote to staging and create a release in GitHub at the appropriate commit.
I suggest we follow a similar approach with AppImage.
This means that each time we push to master we should publish a pre-release called edge-{short-commit-sha}, build and attach the AppImage. Then when we create the actual release (once we are ready in snap too), we should build and attach the AppImage to that release.
Snap has its own version numbering such that each time we push to master the version number is incremented. We obviously can't have the same version number for AppImage as we do not know what it will be at build time. Therefore I suggest we use the short-commit-sha instead.
Current situation with snap is that each time we push into
mastera snap build is triggered in snapcraft which publishes to theedgechannel. These are then tested and promoted to beta inside snapcraft once we're happy with the feature developed.Once testing is complete we promote to staging and create a release in GitHub at the appropriate commit.
I suggest we follow a similar approach with AppImage.
This means that each time we push to
masterwe should publish a pre-release callededge-{short-commit-sha}, build and attach the AppImage. Then when we create the actual release (once we are ready in snap too), we should build and attach the AppImage to that release.Snap has its own version numbering such that each time we push to master the version number is incremented. We obviously can't have the same version number for AppImage as we do not know what it will be at build time. Therefore I suggest we use the
short-commit-shainstead.