Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release process generate (bin distributed) #283

Open
avelino opened this issue Nov 12, 2017 · 7 comments
Open

Release process generate (bin distributed) #283

avelino opened this issue Nov 12, 2017 · 7 comments

Comments

@avelino
Copy link
Member

avelino commented Nov 12, 2017

We need to start generating vim-bootstrap launch (binary), simplifies the process of generating rpm, dev and etc.

@avelino
Copy link
Member Author

avelino commented Dec 13, 2017

We can use the goreleaser by @caarlos0 (Help us in implementing 😄)

@caarlos0
Copy link

Hi there =D

@caarlos0
Copy link

well, let me know what you need =)

@avelino
Copy link
Member Author

avelino commented Dec 13, 2017

We need to create a generating release mechanism (make release by example), what do you propose?
The idea is to generate releases (documenting updates), will be distributed via release from Github[1].

[1] https://github.com/avelino/vim-bootstrap/releases

@caarlos0
Copy link

I usually have a github personal token with repo access and add it to my CI (which is configured like this -> https://goreleaser.com/#continous_integration ) and then whenever I want to release I just push a tag and wait for the CI to do the work for me.

I've seen some people also tagging and running goreleaser locally, something like tag=v1.2.3 make release which does a git tag $tag && git push origin $tag && goreleaser --rm-dist or something like that...

I personally prefer the CI-working-for-me model though :)

@caarlos0
Copy link

FWIW I also have a small cli to do things like svu minor which will increase the minor and print the tag... so I could git tag $(svu minor) or whatever...

will polish it a little and make it public :)

@caarlos0
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants