-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Prepare v0.6.0 #1434
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
Prepare v0.6.0 #1434
Conversation
| * Abhijith Muthyala | ||
| * Adam Ryczkowski + | ||
| * Alex Lembcke + | ||
| * Anton Ballmaier + |
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.
| * Anton Ballmaier + | |
| * Anton Ballmaier |
I have authored a patch in 0.5 as well. Other names may be wrong as well?
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.
Can you link the PR? This will help to debug the dev_changelog.py script.
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.
The issue here is that your name changed between v0.4.0 -> v0.5.0 and v0.5.0 -> v0.6.0 from AntonBallmaier to Anton Ballmaier with a space -- our script works by pulling the author name and comparing author names from the set of past contributors to current contributors with the git shortlog command. I suppose we could do it based on a combination of email/user, but maybe there's a better approach using GitHub's API.
| The parameter `path_arc` of :class:`~.Transform` now works with the `.animate` syntax | ||
|
|
||
| * `#1364 <https://github.com/ManimCommunity/manim/pull/1364>`__: Added :meth:`~.Mobject.match_points` | ||
| - Added :func:`~.Mobject.become_points`, which transforms the points, positions and submobjects of a Mobject to match that of the other while keeping style unchanged. |
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.
CC @Darylgolden
| - Added :func:`~.Mobject.become_points`, which transforms the points, positions and submobjects of a Mobject to match that of the other while keeping style unchanged. | |
| - Added :meth:`~.Mobject.match_points`, which transforms the points, positions and submobjects of a Mobject to match that of the other while keeping style unchanged. |
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.
LGTM
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.
can you change it in the PR title, then behackl would render this again?
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.
I've already taken care of it. 👍
|
I fixed some more broken formatting and fixed a few links; I'm more or less fine with the current state of this. I'll be away for a few hours, everyone with write access can re-run the script though (or push changes to the changelog directly). |
|
Also, can I ask how the list of contributors who reviewed PRs is determined? I tried to review several PRs this release, even though I don't have write access. |
https://github.com/ManimCommunity/manim/blob/master/scripts/dev_changelog.py#L92 If you go to the |
I'm pretty sure I did that several times. |
I'm not really sure what the issue is. We're not doing any filtering on whether the review is of type ^This is what the github package is doing https://github.com/PyGithub/PyGithub/blob/master/github/PullRequest.py#L729-L739 |
|
I initially thought the issue was write access, but there are people without write access in the reviewers list too 😕 |
|
I also think @hydrobeam reviewed some PRs but isn't included too, such as at #1430 |
|
Thanks for making the pr, I just saw that my name is also not there in the "have been reviewed" section. |
|
For those not in the reviewer list: can you check whether you have a name set in your github profile? If not, then that's the issue. I think we can fix the situation by using the login name if no actual name is set. |
I did not set my name, but it is set now :) |
|
I've also set my name 🚀 |
| * Aron | ||
| * Aron Fischer |
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.
I think both the names are the same right? @cobordism
|
I've set my (fake) name |
|
PRs #1434 (obviously) as well as #1282 #1200 #1259 were not yet included in the list because their merge message have either been modified, or because they were merged manually/differently. I've added them now manually. Also, I've changed the logic of how authors are determined -- it now also uses the GitHub API, the names in the authors and reviewers list should now be consistent. |
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.
I'm approving this in advance with these changes (Gotta make the first PR look great and remove the malformatted bullets); however, I'd like to mention that there could be a more consistent grammar/authoring of this text. As is, it appears to be written by various authors and in some cases there's redundancies between the PR title/body text. We'd be here all day doing nitpicks and the meaning is understood nonetheless... so I'd rather just release this considering the tradeoff.
for more information, see https://pre-commit.ci
Co-authored-by: Jason Villanueva <[email protected]>
|
I won't regenerate the changelog at this point, I think it is good to go. (Certainly not written uniformly, and some information might be redundant -- but I don't think there is a wide margin for improvement here.) Pretty impressive work everyone, and thanks for reviewing the changelog! I'll merge and then release soon™️, if you have further comments or remarks, it's either now or never. |

Changelog