Skip to content

Conversation

@behackl
Copy link
Member

@behackl behackl commented Jan 31, 2021

Preparations for new release:

  • Version number bump (to v0.3.0)
  • Include list of changes since v0.2.0

For the sake of documentation, here is what I did to get to this changelog:

  1. git log --format="- %s" --first-parent 8a673946.. > changelog, this creates a file changelog with one line per commit on master
  2. Regex-replacement:
    - (.+) \(#(\d+)\)$
    
    to
    - :pr:`$2`: $1
    
  3. Fix possibly remaining Merge pull request ... from non-squish merges and make them consistent with other entries
  4. Go through the list from bottom to top, classify into Breaking Changes, New Features, Bugfixes and Enhancements, some messages were prefixed by Bugfix:, etc. -- delete these in favor of placement in correct category.
  5. Look through list and add references/code literals wherever it makes sense.

@behackl behackl added the release A tracking issue for changes expected for a release label Jan 31, 2021
@behackl behackl added this to the Release v0.2.1 milestone Jan 31, 2021
Co-authored-by: KingWampy <superpie@usa.com>
pyproject.toml Outdated
[tool.poetry]
name = "manim"
version = "0.2.0"
version = "0.2.1"
Copy link
Member

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.

Copy link
Member

@jsonvillanueva jsonvillanueva Feb 1, 2021

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)

Copy link
Member Author

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).

Copy link
Member Author

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.

@naveen521kk
Copy link
Member

@behackl Do you have any ideas of using https://github.com/twisted/towncrier?

@behackl
Copy link
Member Author

behackl commented Feb 1, 2021

@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.

@behackl behackl changed the title v0.2.1: prepare new release v0.3.0: prepare new release Feb 1, 2021
@eulertour eulertour merged commit 261c28b into master Feb 2, 2021
@eulertour eulertour deleted the prepare-v0.2.1 branch February 2, 2021 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release A tracking issue for changes expected for a release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants