-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Release 7.1.0 #1304
Release 7.1.0 #1304
Conversation
I'd like #1309 to be merged before release so there is consistent use of dialogs not infobar. |
It would be nice if #1320 could be merged too as this is a really annoying issue. |
* Correct links to issues and sort * Add recent issue fixes * Update for pull #1336
Just noticed a new regression which needs looking into before release. |
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 release tag date is a bit old at this point but I think this is ready for review/approval unless you want a little testing done for the full release
@zeebok Yes, I wanted to do a few days testing before updating the release date and marking ready for review. Probably be ready beginning of next week. Need to update the metainfo too. |
Should you include the issues in that top checklist in the metainfo? |
@zeebok I only include fixes for issues that were present in the last released version of Code or that have some significance to the user (like new/changed features/appearance). Things like correcting problems with a recent unreleased commit or code cleanups are not included. I think the regressions were all caused by unreleased commits so I did not include them. If I have missed something that changed something in the last released version please let me know. |
<Ctrl>F
can reload a previous search unexpectedly. Fixed by Search entry reverts to previous term after editing and<Ctrl>f
#1335