Prepare for 3.0.3 release #656
Conversation
|
It is very encouraging to see the recent activity and the approaching 3.03 release. Concerning 630, even a partial fix would be a worthwhile improvement. |
|
I would love to see some discussion on projecthamster/hamster-shell-extension#334 and see wether we prefer to revert 42d3c05 here or find some other solution elsewhere. |
Good point, I had missed that. I created a separate issue for that: #657 |
matthijskooijman
force-pushed
the
release-3.0.3
branch
from
4f1cade to
70e2547
Compare
|
Hi @matthijskooijman what about small PR like #690 and #699 ? |
|
I think everything is still ready for a next release. @elbenfreund can you do a new release? |
|
Some distros like Manjaro have already updated to python versions where the 3.0.2 release is not starting anymore (#726). I think it would be time to make a new release to fix this issue. |
|
Automatically generated build artifacts for commit 7fd3f9c (note: these links will expire after some time):
To test this PR, download and unzip the flatpak application above and then install with: |
|
Automatically generated build artifacts for commit 187cd70 (note: these links will expire after some time):
To test this PR, download and unzip the flatpak application above and then install with: |
|
Automatically generated build artifacts for commit bf9b764 (note: these links will expire after some time):
To test this PR, download and unzip the flatpak application above and then install with: |
|
Automatically generated build artifacts for commit ebe5367 (note: these links will expire after some time):
To test this PR, download and unzip the flatpak application above and then install with: |
|
I'm going to close this for now, and then make a new PR with a clean history for the final release. |
This PR starts adding some release notes for previously merged. This replaces #614, but this PR is created from a branch in this repository, making it a bit easier for all maintainers to update it as we go along.
As for release planning: I'd like to move to a 3.0.3 release, since we've already collected some relevant bugfixes in master. I would like to at least also merge #630 before releasing, which fixes the worst usability issues in the edit activity screen (but needs a bit more work, probably from my side).
Any other things that we would want to get into this release? I looked through the open PRs, but most of the recent ones still need more work, and the older ones need a better looking-at. #631 might be easy, but I haven't taken the time to review it yet (and I probably won't want to delay release for it).