Pending task for new process of releasing with golang migration

[subhamkrai]

These are steps we need to do for releasing with go

• Clean the project by removing bash content. Fixes: clean: removing all the content related to bash #127
• Add goreleaser for releasing the binary in all the possible supported formats. It will help in releasing binary in different os with different architecture. Fixes: ci: add goreleaser to build the project #126
• update .krew.yaml to reflect the golang binary with the right version. Fixes: krew: update krew yaml to reflect change to go #128 ( prnot ready for review)
• Finally, before releasing do the testing, by going inside goreleaser ci runner and confirming the binary is working as expected.

[subhamkrai]

@travisn I created the issue so that we are all on the same page regarding adding the changes for the new release

[travisn]

When someone upgrades the krew plugin, will the bash script be automatically removed? Or is there any manual cleanup?

[subhamkrai]

When someone upgrades the krew plugin, will the bash script be automatically removed? Or is there any manual cleanup?

I assumption is krew should handle that automatically.

[travisn]

When someone upgrades the krew plugin, will the bash script be automatically removed? Or is there any manual cleanup?

I assumption is krew should handle that automatically.

Is there a way to test the new release before it's officially out? Then we can confirm that the upgrade is smooth for the transition.

[travisn]

btw let's wait until early next week for the release so we don't have a release just before the weekend

[subhamkrai]

btw let's wait until early next week for the release so we don't have a release just before the weekend

Yes, I have a few testing with migration to do I have found this https://krew.sigs.k8s.io/docs/developer-guide/testing-locally/ to test locally exploring how we can test this.

[subhamkrai]

also holding this pr #128 till above testing is done

[subhamkrai]

btw let's wait until early next week for the release so we don't have a release just before the weekend

Yes, I have a few testing with migration to do I have found this https://krew.sigs.k8s.io/docs/developer-guide/testing-locally/ to test locally exploring how we can test this.

I did manual testing it was working but the testing process is not the same as the one we have in CI, since ci is full automation and one ci depends on another CI. We can follow up offline

[subhamkrai]

All task is done.