You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What if we start introducing version? Now that we created the library, it's a good idea to introduce the versioning concept. We can use the "Milestone" Github feature, and introduce the appropriate code sections.
I think we can start with version 1.0 by adding the following features:
Then later, we can add some other features. Another thing to decide: subversioning goes up by 1 or by 5? i.e. 1.x branch has next subversion 1.1 or 1.5 (and then 1.2 or directly 2.0?).
The text was updated successfully, but these errors were encountered:
I like the idea, but I'm not sure the added formality does anything for us. In your mind, what's the benefit for doing versioning? PyPI and packaging? (because that might be worth thinking about soon)
What if we start introducing version? Now that we created the library, it's a good idea to introduce the versioning concept. We can use the "Milestone" Github feature, and introduce the appropriate code sections.
I think we can start with version 1.0 by adding the following features:
Then later, we can add some other features. Another thing to decide: subversioning goes up by 1 or by 5? i.e. 1.x branch has next subversion 1.1 or 1.5 (and then 1.2 or directly 2.0?).
The text was updated successfully, but these errors were encountered: