-
Notifications
You must be signed in to change notification settings - Fork 943
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
v1.2.0 Taylor Release #1599
Comments
There are lots of recent PRs that are not tagged (https://github.com/projectmesa/mesa/pulls?page=1&q=is%3Apr+no%3Amilestone+is%3Aclosed). Though I forgot the reason why all of them have to be tagged to a milestone for a release. I thought issues in milestone are reserved for only the ones that are necessary and are blocking the release itself. |
@rht I had always done it as a tracking mechanism to try to correlate with history -- it is mostly focused on PRs so they are easy to find. |
We could collect them all by the timestamps (all recent merged PR's after the release PR) and put them in the HISTORY.rst. I don't see having to find the release tag of a PR to be a common use case. But I'm fine with having to tag the recent merged PRs as usual too. |
@rht I think what you are suggesting is an automated process. We talked about that... let's revisit setting that up. I am going to do a manual tag for now before we switch to something new. |
@rht, @tpike3 can either of you do a review of everything I tagged? |
@rht - do you have any preference of history format? |
There are old PRs/issues that have been accidentally tagged in https://github.com/projectmesa/mesa/milestone/32?closed=1. I have untagged them. One feature with associating PRs with a milestone of a release is that you can track which release a PR is a part of, from its milestone. But this info is not used that often. Other projects use them for blocking issues:
I have no preference for the history format (at the moment). |
Currently on a plane, but unable to push PRs. Here is a draft on history -- Feel free to this directly & comment generally on the changes. Also, what do we want to highlight in the Special notes? 1.2.0 (2023-03-09) Taylor Special notes New features:
Some highlights for the perf improvements:
Improvements
Fixes
|
@tpike3 ^^ Can you make sure any updates you pushed over the weekend are included? |
This one was merged in the examples repo. |
New features: Some highlights for the perf improvements:
Those are harder to find from the PR list because the PR titles don't explicitly have "perf:" prefix. |
@rht Thanks! @jackiekazil I have nothing else to add. That is an impressive list. |
Yes, I will make sure that perf commits will have perf: prefix in the future. |
https://pypi.org/project/Mesa/ |
Last release was v1.1.1 (2022-10-10) Safford
^^ This was the last release.
Prep v1.1.2 Release
The text was updated successfully, but these errors were encountered: