Version the spec itself about spec HOT 5 OPEN

I think instead of that we could introduce engines field, just like in npm.

"engines" : { "bower" : "~1.4.0" }

from spec.

To clarify, are you suggesting using the Bower CLI tool's version number in engines or a spec-specific version number?

The problem with the former is there's (vexingly) no good correspondence between the Bower CLI tool and the spec. Also, e.g. if the Bower CLI tool added a bunch of wizards for doing things, that would necessitate a minor version bump, but bumping the engines version would be unnecessary busy work.

from spec.

I mean version of bower used (not the spec). As you said, there's not enough correspondence between bower and spec, so it's safer to require given bower version than the version of spec. Spec could define what bower version implements what (if any version implements it at all).

I don't think we need wizards for that.

from spec.

"bower" would be the only valid key in engines, correct?

from spec.

I'm working on custom resolvers feature, so I guess we could include them as well..

from spec.