Removing v1alpha2 version (#136)

Author: johnugeorge

.travis.yml

@@ -13,7 +13,6 @@ install:
   - gometalinter --install
 
 script:
-  - go build -o pytorch-operator.v2 github.com/kubeflow/pytorch-operator/cmd/pytorch-operator.v2
   - go build -o pytorch-operator.v1beta1 github.com/kubeflow/pytorch-operator/cmd/pytorch-operator.v1beta1
   - gometalinter --config=linter_config.json ./pkg/...
   # We customize the build step because by default

Dockerfile

@@ -1,6 +1,5 @@
 FROM debian:jessie
 
-COPY pytorch-operator.v2 /pytorch-operator.v2
 COPY pytorch-operator.v1beta1 /pytorch-operator.v1beta1
 
 ENTRYPOINT ["/pytorch-operator", "-alsologtostderr"]

build_image.sh

@@ -20,8 +20,6 @@ echo "Create symlink to GOPATH"
 mkdir -p ${GOPATH}/src/github.com/kubeflow
 ln -s ${CONTEXT_DIR} ${GO_DIR}
 cd ${GO_DIR}
-echo "Build pytorch operator v1alpha2 binary"
-go build github.com/kubeflow/pytorch-operator/cmd/pytorch-operator.v2
 echo "Build pytorch operator v1beta1 binary"
 go build github.com/kubeflow/pytorch-operator/cmd/pytorch-operator.v1beta1
 

cmd/pytorch-operator.v2/app/options/options.go

@@ -4,7 +4,7 @@ This folder contains an example where mnist is trained. This example is also use
 
 The python script used to train mnist with pytorch takes in several arguments that can be used
 to switch the distributed backends. The manifests to launch the distributed training of this mnist
-file using the pytorch operator are under the respective version folders: [v1alpha2](./v1alpha2) and [v1beta1](./v1beta1).
+file using the pytorch operator are under the respective version folders: [v1beta1](./v1beta1).
 Each folder contains manifests with example usage of the different backends.
 
 **Build Image**