Implements scripts to cut a release

[knative]

Implements scripts to cut a release

[rhuss]

An idea for setting the release number properly during build and release, together with the PR in #69 which introduces a kn version command:

• Using a file e.g "NEXT_VERSION" with a single entry (e.g. "0.1.0").
• A build.sh which uses

go build -ldflags "-X commands.Version=$(cat NEXT_VERSION)-$(git rev-parse --short HEAD) ....

for setting a snapshot version (according to semver.org 1.0.0-eed913e is before 1.0.0)

• A release.sh which uses

go build -ldflags "-X commands.Version=$(cat NEXT_VERSION) ..."

and then increases the number in NEXT_VERSION to the next milestone version.

[maximilien]

@rhuss let me know if the scheme in #69 is good enough. Best.

[rhuss]

Looks good, I think its good enough for now. Thanks !

[csantanapr]

/milestone v0.1.0

[knative-prow-robot]

@csantanapr: You must be a member of the knative/knative-milestone-maintainers github team to set the milestone.

In response to this:

/milestone v0.1.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[maximilien]

Parts of this done in #69