Vyper: Make a release/tag on github when updated version in setup.py

[djrtwo]

What's your issue about?

Cutting a release/tag via github can be useful in certain environments when trying to specify an exact state of the codebase.

How can it be fixed?

Release 0.0.3 via github and release future versions via github.
Add this to your release process.

Cute Animal Picture

[fubuloubu]

I like tagging versus releases, thoughts @DavidKnott?

[karlfloersch]

@DavidKnott !!!!!!!!!

[jacqueswww]

Tagging and releasing is cool, if we have a goal to do this for ie. "stable release for beta auditing" for example.
If someone wants a frozen part of the code base they could just use the commit hash right?

[jacqueswww]

That being said, we at some point need tagging & releasing for pypi for example so @DavidKnott: "You got the power" :stuck_out_tongue:

[djrtwo]

bump

[jacqueswww]

@djrtwo I think the best option is that we start release tags, once we mark Vyper as beta, this is hopefully soon ;) as I don't see any critical features missing (anymore).

[djrtwo]

Sooner the better! We are using it in some Casper repos and it would be
very useful. Even an alpha tag

On Sunday, March 4, 2018, Jacques Wagener [e-mail] wrote:

@djrtwo https://github.com/djrtwo I think the best option is that we
start release tags, once we mark Vyper as beta, this is hopefully soon ;)
as I don't see any critical features missing (anymore).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/vyper/issues/681#issuecomment-370170147, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABXf-4vJX_agHe6cw95_UAfExCeY_DSYks5tauQ9gaJpZM4SHK1h
.

[jacqueswww]

@fubuloubu I shall tag an alpha today or tomorrow. Let's see how it goes :)

[djrtwo]

@jacqueswww Should we close this issue or should the tag/release process make it into the readme or something?

[fubuloubu]

We should have a "how to contribute" section

[jacqueswww]

I think we can close it for now. I want to to take a simple approach for now to just tag a release every 1-1.5 months. Which hopefully means 0.0.5 will effectively be the beta.

[fubuloubu]

@jacqueswww I would disagree. Per PEP 440 (which we are following), we should at least be revved to 0.1.0 before we begin beta (maybe 0.1.0b1 to start). We have to rev the beta number for every collection of released fixes until it is fully released. We could also do a major version to start, e.g. 1.0.0b1 to make it more clear this is aiming for first major release.

Just tagging every month or so is not the correct approach, it should be tired to feature updates per PEP 440.

[jacqueswww]

@fubuloubu sure we can do so. Next tag will be 0.1.0b1 then, after mapping and bytes has been done.

[fubuloubu]

:+1: