aniero/janus — comment on commit e8b3e65f24cf6bb84ae6b007358362d4270c20be
File:  line 0
By eMxyzptlk:

This is not acceptable, it is our job (The janus team) to update and lock the plugins, it is not up to the user to update the plugins after each time he runs rake, if we pull this, we might as well switch back to master but use pathogen to load them..

Consider the following example, we've updated Command-T and then later we've been alerted that it has a regression, until it has been fixed upstream all we have to do is revert the update and voila the user will get the fix after he runs `rake`, but if running `rake` will also update submodules regardless if the version locked in Janus, the user will not be able to fix his command-t issues even though we've reverted the update

The idea behind the Experimental branch is simple, Vim-way, stable, easily manageable and configurable distribution (we're not there yet but we're [working on it](https://github.com/TechnoGate/vimius))