Release v2.45.0 #2467
Comments
|
#2454 is the only PR that stands out as something we might want to push in. A lot of the current PRs are code cleanup, documentation, and other internal changes. These changes are important, but since they're not user-facing it doesn't particularly matter if they get in before or after a release. |
|
#2454 not ready yet IMO. |
|
I'd prefer to release 2.45.0 without #2454, I agree it needs some more work. |
|
I also think #2454 is not ready. Merging now would break current review process and this is rather important change, like all the other road rendering changes. I was rather thinking about long overdue PRs and small code changes which need just a final touch. I have updated latest changes in CHANGELOG.md, please take a look if the wording is clear before release. |
|
Next step - updated preview.png, because construction and pitch color are changed since last rendering. It was done through the GitHub UI, just like the Changelog, which is also now ready for release. |
|
Ok, new release is out and waiting for deployment on OSM servers. The only thing left is:
Should I really do that? |
|
I don't think we have been doing that over the past few releases, but maybe we should. |
|
You're right, a difference is quite big now. I don't feel like touching it to not spoil anything, so I leave it to @pnorman probably. BTW: Why do we require Noto Emoji font? It holds back deployment on OSM servers. |
I have. I can do this release too. |
|
Thanks, I consider this issue to be resolved now. |
I think it's time to release v2.45.0 and I guess it's good to make it in a transparent way, so the new maintainers, including me, could learn the process in practice (basics are described in RELEASES.md). One can see current unreleased changes here:
v2.44.1...master
Which PRs do you think should be merged before the release? I like our current release time frame (every month or so) and would like to keep it.
The text was updated successfully, but these errors were encountered: