deathaxe

I am quite far with my solution for Issue #26 which also brings along significant lower latencies to add the gutter icons especially for large files. The work is mainly...

Can you check PR #351, #354, #355, #356 for remaining issues, please? I am nearly complete with preparing a PR to fix the following issues on top of those commits:...

### Release strategy @jisaacks: Continued discussion from #359 When calling the `git: generate changelog` it asks for the tag to compare against with the most recent one as default value....

You mean: `1.5.0-pre.1` - tag with maybe new features `1.5.0-rc.1` - feature freeze for bug fixing only Thanks for the tip!

@jisaacks: As `GitGutter-Edge` is already removed from package control repositories we may 1. decide how to tag pre-releases 2. mark the master as pre-release on some good state 3. publish...

Ok, will rebase the PR branches, autosquash the fixups and generate a PR with the changelog.

Thank you very much for patiently testing my changes! Cool to get these results publishedm soon. Maybe this is a good time to think about what could come after 1.5.0....

### release message > I see you added a message for 1.5.0 in release_messages/src This is good. But it's actually the release_messages/dest that package control uses to generate the releases....

I am a bit confused about the packagecontrol.io stats. With GitGutter not in the list of `install_prereleases`, _Package Control_ installs 1.4.0 as expected. With GitGutter in that list _Package Control_...

With the merge of PR #378 I am done with preparations for a final 1.5.0 release. Now it's up to @jisaacks when and how to make the final cut including...