Call build-go.sh before bundling a release

Now the dev-build-and-* scripts actually work.
It's not at all obvious that this is about autogenerated files.  Should we
bust that out to a distinct step?  Why not just write a Makefile...


On Mon, Aug 4, 2014 at 2:01 PM, Daniel Smith <notifications@github.com>
wrote:

> In hack/dev-build-and-up.sh:
>
> > @@ -17,11 +17,17 @@
> >  # This script will build a dev release and bring up a new cluster with that
> >  # release.
> >
> > -# First build a release
> > +# First build the binaries
> > +$(dirname $0)/build-go.sh
>
> Should this actually be part of building a release? Do you ever want to
> build a release without triggering the autogeneration of the version file?
> (and first verifying locally that stuff builds...)
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/774/files#r15780797>
> .
>