-
Notifications
You must be signed in to change notification settings - Fork 281
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
v0.27.5 #1983
v0.27.5 #1983
Conversation
Codecov Report
@@ Coverage Diff @@
## 0.27-maintenance #1983 +/- ##
=================================================
Coverage 46.36% 46.36%
=================================================
Files 146 146
Lines 23005 23005
Branches 11809 11809
=================================================
Hits 10666 10666
Misses 6689 6689
Partials 5650 5650 Continue to review full report at Codecov.
|
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.
LGTM
@alexvanderberkel @postscript-dev @hassec @piponazo @1div0 @dhoulder @kevinbackhouse @kmilos Exiv2 v0.27.5 is on the web-server for inspection. If nobody reports issue with this, I will tag and publish the code on GitHub on 2021-10-22 at 16:00 UTC. Alex: Can you make the following announcement on Facebook and discuss.pixls.us on Friday evening. Exiv2 v0.27.5 is available: https://exiv2.org/ A huge thank you to Kev for his hard work on Exiv2 Security. Great Job, Kev. Thank You, David for the CR3/Preview code. Thank you to Alex, Christoph, Luis, Milos, Peter K, Peter S and Robin for working on this release. Highlights of Exiv2 v0.27.5
Release Notes: #1018 (comment) |
I noticed a small thing in the windows release (see #1984) , but it is nothing serious. I would not delay the release of 0.27.5 just for that. It is something that can be dealt with for the next release. |
Builds, tests and runs fine for me. gcc 9.3.0 reports a bunch of deprecation warnings about auto_ptr, but that's about it. Thanks everyone for your help. Is there some way to let the distro package maintainers for Ubuntu, Fedora, Suse etc. know that they should build with |
Yes, the README ;) Joking aside, for Fedora it is undergoing a legal review, you can check the build recipes for the rest if you'd like to make sure... |
I don't know anything about the distro people. They do a great and important job. Remarkably, I don't recall any correspondence with them. There's a web-site "Linux From Scratch" that provides recipes for packages. https://www.linuxfromscratch.org/blfs/view/svn/general/exiv2.html I was surprised that they recommended We need an Exiv2 Team meeting to discuss the future. I promise to attend and not to speak unless asked a direct question. Com'on @alexvanderberkel. Can you set up something on Zoom. Saturday 13 November? |
The Release is tagged and published. https://github.com/Exiv2/exiv2/releases/tag/v0.27.5 @kevinbackhouse You did some magic with RC3 to get the CI to build some binaries and you added them to the GitHub Release. Very happy if you could repeat that exercise. Very happy to have reached this point. I've enjoyed today and discussed stuff with David and Luis and Milos. I know Exiv2 is in safe hands. Thank You everybody who contributes. Together we've achieved a great deal. |
@clanmills: Thank you for creating this release! |
Big thank You, @clanmills for every line of code! Cheers. |
Done |
Good! I hope Team Exiv2 have a meeting in the next couple of months. I'll be happy to attend as an "observer". |
No description provided.