-
Notifications
You must be signed in to change notification settings - Fork 2.5k
v0.3.0: prepare new release #986
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
Conversation
Co-authored-by: KingWampy <superpie@usa.com>
pyproject.toml
Outdated
| [tool.poetry] | ||
| name = "manim" | ||
| version = "0.2.0" | ||
| version = "0.2.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be 0.3.0? We didn't do a mid-month release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're using semantic versioning, then points 4, 6 and 7 are useful references. I think this release adds a few new backwards compatible features and would justify bumping the minor instead. Perhaps future month releases will only involve bug fixes/patches, but I foresee many minor bumps as we add new features each month to the core (I'm calling it here, 0.11.2 -> 1.0.0 -- only half joking)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as our major version is still 0, that doesn't really apply though necessarily. That being said, I'd be fine with bumping to v0.3.0 (although I was thinking of moving to v0.3.0 only with the switch to the webgl renderer).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the discussion on Discord it seems that people are either neutral or leaning towards v0.3.0 -- so let's adhere to semantic versioning, respect that we've introduced new, backwards-compatible features, and let's go with v0.3.0. I'm pushing another commit.
|
@behackl Do you have any ideas of using https://github.com/twisted/towncrier? |
No, and I don't really see a reason for using it. |
Preparations for new release:
For the sake of documentation, here is what I did to get to this changelog:
git log --format="- %s" --first-parent 8a673946.. > changelog, this creates a filechangelogwith one line per commit on masterMerge pull request ...from non-squish merges and make them consistent with other entriesBreaking Changes,New Features,Bugfixes and Enhancements, some messages were prefixed byBugfix:, etc. -- delete these in favor of placement in correct category.