minor #6043 Mention commiting only bower.json (krike, WouterJ)

This PR was merged into the 2.3 branch.

Discussion
----------

Mention commiting only bower.json

Replaces #5778

| Q | A
| --- | ---
| Doc fix? | no
| New docs? | yes
| Applies to | all
| Fixed tickets | -

The section is called "Should I Git Ignore or Commit Bower Assets?", but we cover only the commit way and not the git ignore way, giving users a bit biased information. We should at least mention that people can also commit bower.json.

Thanks to @KriKe for providing the original patch!

Commits
-------

d701e3d Rewrite section about bower.json
1a98bca Add mention for Bower.json

Author: xabbuh

cookbook/frontend/bower.rst

@@ -135,6 +135,12 @@ For more details, read the article `Checking in front-end dependencies`_.
 But, it's very possible that Bower will add a lock feature in the future
 (e.g. `bower/bower#1748`_).
 
+If you don't care too much about having *exact* the same versions, you can only
+commit the ``bower.json`` file. Running ``bower install`` will give you the
+latest versions within the specified version range of each package in
+``bower.json``. Using strict version constraints (e.g. ``1.10.*``) is often
+enough to ensure only bringing in compatible versions.
+
 .. _Bower: http://bower.io
 .. _`Node.js`: https://nodejs.org
 .. _BowerPHP: http://bowerphp.org/