joshuaskelly / twitch-observer

Turn Twitch chatter into Python events
MIT License
26 stars 6 forks source link

Regarding Versioning #68

Closed PythooonUser closed 6 years ago

PythooonUser commented 6 years ago

Summary

As of recent questions and maybe a slight confusion on my end (:P) I want to ask a question regarding the project versioning.

@joshuaskelly already mentioned we use semantic versioning, i.e. [major][minor][patch].

My question is more of an organizational nature. When do we increase the version?

Also, should increasing the version be part of the PR? Or done after that seperatly?

Personally, I would favour option two and having the version bumping done afterwards.

Thoughts?

PythooonUser commented 6 years ago

I created a v0.10.0 milestone and assigned issues to it.

senpos commented 6 years ago

After a specific time frame of development?

I'd go with it.

Merge PRs and then add new commit with version bump, when things are ready for new release.

Or even better - gather the issues and plan a new version release with all of them are fixed. Let's say, we want commands and docs to be done in 0.10.0.

upd. Oh, milestone is a cool feature!

joshuaskelly commented 6 years ago

We should bump the version number before we publish.

Thanks for creating a milestone @PythooonUser !

PythooonUser commented 6 years ago

Alright! Milestone it is. Closing.