Vundle installs an out-to-date version (default source) or the development version (github source)

[setempler]

Hi,

First of all, thanks for sharing and continuing to work on improving the plugin.

Using vundle to install the script, I noticed that either the version is outdated, using

Plugin 'gnupg.vim'

or it is at the latest development commit, not the latest release, using

Plugin 'jamessan/vim-gnupg'

---

For the first method, I obtain v2.5, which is pulled from https://github.com/vim-scripts/gnupg.vim.

For the second method, I obtain HEAD of this repository's master branch (currently 22cbc6b) which is a development commit, and not the (latest) release commit (currently v2.6.1 966808d).

So I would need to use the second method, and in addition checkout the release tag, which is complicated:

cd ~/.vim/bundle/vim-gnupg
git checkout v2.6.1

I'd love to use PluginUpdate with vundle instead.

---

Would you mind to either

• update the code at vim-scripts w/ the latest release or
• create a development branch, only merging tagged/released commits/versions to master, so the checkout/update (via vundle) points to a release?

Many thanks!

[jamessan]

master as the main development branch is a very common development model. Every plugin I use follows that. I'm sorry that vundle makes it difficult to deal with that.

[jamessan]

update the code at vim-scripts w/ the latest release

I have no control over when vim-scripts/gnupg.vim is updated. That's up to whoever runs that service.