Skip to content

Commit

Permalink
Fixing instructed version references to actually use the branch-alias…
Browse files Browse the repository at this point in the history
… so it properly handles when versioned are tagged and branch aliases increase
  • Loading branch information
r4j4h committed Dec 5, 2014
1 parent 4d88291 commit 6ae157a
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,10 +68,10 @@ Implementation wise, this can look like:
How to Install
---------------

Right now, there is no tagged version.
Right now, there is no tagged version. To be ready for it when it comes, branch-aliases are in place.

- Stable branch: `~1.0-dev`
- Cutting edge: `dev-develop`
- Stable branch: `~1.0@dev`
- Cutting edge: `~1.1@dev`


To install, it is suggested to use [Composer](http://getcomposer.org). If you have it installed, then the following instructions
Expand All @@ -80,7 +80,7 @@ in a composer.json should be all you need to get started:
```json
{
"require": {
"r4j4h/php-druid-query": "~1.0-dev"
"r4j4h/php-druid-query": "~1.0@dev"
}
}
```
Expand Down Expand Up @@ -165,7 +165,7 @@ Appendix A. Composer.json example that does not rely on Packagist.org:
}
],
"require": {
"r4j4h/php-druid-query": "~1.0-dev"
"r4j4h/php-druid-query": "~1.0@dev"
}
}
```

0 comments on commit 6ae157a

Please sign in to comment.