Brendan Forster

@thwaller cool, sounds like we've got some cases that are not the AppImage (and just PopOS being out of date) so it's hard to keep this focused on that area.

I've published an update that should resolve this - [`2.8.1-linux2`](https://github.com/shiftkey/desktop/releases/tag/release-2.8.1-linux2). Please test it out and confirm this is resolved for you.

I'm not familiar with what this involves - got any links or resources to help orient myself?

Tagging this as `help wanted` to indicate that I'd love some help with adding this support to CI, so I can at least validate that I'm not affecting the downstream...


> I image that once we get enough feedback and turn around that we have a syntax version that works as a feasible first cut, we would create the first...

+1 to discussing this "processor" concept. Given you're using semver to label a releases, why let people over-complicate them? Using a filename to represent the version makes it easy to...

> I think convention is key to most of this being easy and logical. I've got some ideas for tooling where we stick to `major.minor` releases for a codebase (and...

I'm skeptical on the need for this because other systems will take care of tracking this release date for me. For example: - RubyGems - http://rubygems.org/gems/jekyll/versions - NuGet - http://nuget.org/packages/Mahapps.Metro/...

@nikmd23 i'm on board with enhancing #2 to indicate that build and pre-release tags are supported. That matrix is an excellent overview of the options available. > The + character...