Commit graph

8 commits

Author SHA1 Message Date
Richard Scothern
35dd23c649 Update AUTHORS and version file
Signed-off-by: Richard Scothern <richard.scothern@docker.com>
2016-05-04 10:22:07 -07:00
Richard Scothern
1ea9a3638d Rev base version to 2.4.0
Now that we've tagged a release candidate, we can now say all builds are
"2.4.0+unknown" if the makefile is not used.

Signed-off-by: Richard Scothern <richard.scothern@docker.com>
2016-03-28 13:54:28 -07:00
Richard Scothern
7ba21d8b1d update version file
Signed-off-by: Richard Scothern <richard.scothern@gmail.com>
2016-02-04 10:58:06 -08:00
Stephen J Day
6cb14b79f1 Rev base version to 2.1.0
Now that we've tagged a release candidate, we can now say all builds are
"2.1.0+unknown" if the makefile is not used.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-08-06 17:21:03 -07:00
Stephen J Day
aa74de8824 Update rough version for release
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-04-16 11:25:03 -07:00
Stephen J Day
a307ff4471 Update rough version to be closer to reality
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-04-06 19:32:33 -07:00
Stephen J Day
ea50359c05 Update AUTHORS and default version package
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-03-02 23:39:19 -08:00
Stephen J Day
d0abfe0b92 Report version in registry binary
We've added support to the registry command to report the current version of
the distribution package. The version package is generated with a shell script
that gets the latest tag and add "+unknown". This allows builds from "go get"
and "go install" to have a rough version number. Generated periodically, it
will provide a decent indication of what code built the binary. For more
accurate versioning, one can build with the "binaries" make target. Linker
flags are used to replace the version string with the actual current tag at
build time.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-01-29 18:32:01 -08:00