The premise is that this option is a developer aid (not a deployment / provisioning / update tool).   

The presumption is that you will use a `build-version.yml` spec (e.g. included in `server-vars.yml` and either `/edx/bin/update`  (which will read the extra-vars, and act appropriately - i.e., not use this option for paver), or  vagrant provision (same comment, but that would depend on my PR to configuration which has been on the back burner simmering, ready to start now).

My initial concern / reploy to @dangtrinh on this was that there is no need for it (it's only replacing 2 commands for a developer:  a manual `git pull` of the them repo under development, and a `paver update-assets`  (or equivalent superset, e.g. `paver devstack lms`).

@singingwolfboy - your comment here seems to reinforce that initial concern:  this is not only not really useful (and therefore not needed), it could set up a lot of confusion.

@dangtrinh - what do you think about abandoning this?