Remove version prompt from bower init

[sheerun]

Because version has been deprecated in bower spec: https://github.com/bower/bower.json-spec

Right @sindresorhus @benschwarz ?

[sindresorhus]

👍

[unscriptable]

👎 This breaks RaveJS/rave which does runtime inspection of packages from the browser.

[benschwarz]

@unscriptable It'll be a major version bump before this change is actually landed via bower init (however effective in the spec [which few people read] immediately).

Can you perhaps describe your usage for version on the relevant spec issue?

[unscriptable]

Thanks, @benschwarz. done.

tl;dr: the fact that .bower.json is hidden is preventing us from discovering useful (and vital) meta data. If this meta data is now removed from bower.json, we can no longer discover it.

[sheerun]

@benschwarz Are you sure this should be a major, not a minor bump?

[benschwarz]

well… even though we're not really using version, others may be relying on it in their scripts / processing.

I think we should deprecate version in the next point release and state its removal for the next major/minor (probably minor, as its not a break in our API as such) release. Sound sane or am I thinking too hard on this?

[sheerun]

@benschwarz I'm not sure how/when state that