This issue tracks the release note for the following Fedora Change:
If you own this change, please add additional information here that we should communicate to Fedora users. Specifically, please consider:
Your notes to us do not need to be formally written. We will edit them and add details as needed. This is a way for you to ensure that we know what is critical about your change.
If you want to write this release note, then:
Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, AsciiDoc, or whatever else, just add it to this issue as a comment and let pbokoc know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (October 29 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.
 You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure.
 In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc @redhat.com if you can't get a hold of me on IRC.
Metadata Update from @mareksu:
- Issue assigned to mareksu
@smani, I've prepared a release note for the MinGW update in F31. Could you please review it?
== MinGW has been updated
The MinGW development environment and toolchain has been updated to the latest upstream version:
| Component | Updated version
| `mingw-gcc` | 9.1.0
| `mingw-w64-tools` | 6.0.0
| `mingw-winpthreads` | 6.0.0
| `mingw-crt` | 6.0.0
| `mingw-headers` | 6.0.0
| `mingw-binutils` | 2.32
For more information, see the MinGW release notes: link:https://mingw-w64.org/doku.php/versions.
Unfortunately, the link points to a site with an expired certificate. Do you know if there's an alternative website that I could link instead?
Looks good to me thanks, if the certificate error persists you might want to point to the announcement in the mailing list: https://sourceforge.net/p/mingw-w64/mailman/message/36416777/
Thanks, @smani. The certificate issue hasn't been resolved yet so I'm switching to the mailing list link.
Fixed in #405.
Metadata Update from @pbokoc:
- Issue status updated to: Closed (was: Open)
to comment on this ticket.