I'm aware this just an example, but it [leads readers to see it a best practise](40642df5ec (r29802440)).
Having code with `"php": ">=5.4.0"` is pretty dangerous and will probably break with next major version.
```json
{
"require": {
"php": "^5.4"
}
}
```
```json
{
"require": {
"php": "^7.1"
}
}
```
is much more safer. Promoting best and proven practise should from *Basic usage* helps people to use composer the best way they can.
What do you think?
* docs-improve:
Docs: cleanup version branches section
Docs: those/these composer/Composer
Docs: notice => note
Docs: Fix shell sample output
Docs: Add back a second clear note about hardcoded versions in VCS
Docs: HHVM is not called HipHop
Docs: versions plural, and update == rm lock&install
Docs: don't use short forms, it => composer
Docs: composer.lock lists versions, not constraints
Docs: superfluous comma & it => Composer
The confusing part is probably rather constraints and how versions work, not what they are
Docs: Clarify what "It" stands for
Finished reworking docs to clarify points about versioning (fixes#6088)
Updated basic usage and versions pages to clarify how versioning and package resolution works (refs #6088)
Added some useful overview information about repositories in the Basic Usage documentation.
The "next significant release" a.k.a as the tilde version constraint
would not install a pre-release (alpha, beta, RC) which is not in the same
version namespace.
But in the examples so far it was shown as `~1.2` equals `>=1.2,<2.0` which
would actually install `2.0-beta.1`, because it the pre-release is before
the `2.0` release.
See https://github.com/composer/getcomposer.org/issues/64
Note I: This syntax is supported by MarkdownExtra, which both getcomposer
and github are using.
Note II: This patch currently breaks the PDF, because pandoc does not like
non-standard markdown tables. Ideas for fixing this appreciated.
Note III: The idea for this patch came up a few weeks ago on IRC. We
agreed back then that a table would be a good idea.
Note IIII: This patch creates a stability section which opens the door for
finally documenting how stability works in the composer docs.
Tomáš Votruba