-
Notifications
You must be signed in to change notification settings - Fork 540
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
Call for Testers! - v2.8.0 #650
Comments
@k00ni I've just updated the title to find that it was useless at the end 😅 Good to go for me: https://github.com/smalot/pdfparser/releases/tag/untagged-546567f4b175d9d307fc |
Thank you. v2.8.0-RC1 is out: https://github.com/smalot/pdfparser/releases/tag/v2.8.0-RC1 |
Thanks everyone for all your help with this! |
Small note: There is a nice statistic about the amount of installs per version: https://packagist.org/packages/smalot/pdfparser/stats#v2.8.0-RC1 It doesn't cover ALL installations/downloads, but could be a good estimate. |
I've been using it since the day it came out. So far, I have not encountered the problem of corrupted letters in the old versions. I find it more accurate to call this version 3.0.0 instead of 2.8.0. Thanks to everyone who contributed to this version, especially for different languages, we can finally say that we have reached the real version. |
@k00ni good for me! |
We receive too many bug reports which are related to 2.7.0, but not 2.8.0-RC2. In each I have to ask people to try again with our latest release. That consumes too much time and some are not even answering. Also, there are people reporting that 2.8.0-RC2 works for them or the reported bug remains after they updated to the latest version. Because of this I would like to release 2.8.0. Any objections? |
I agree with you, go release 2.8.0 |
This issue combines coordination of the v2.8.0 release as well as collecting related issues/problems.
Ref #634
@j0k3r - OK?
https://github.com/smalot/pdfparser/releases/edit/untagged-929a6f925a01a30df44d (collaborators only)
If someone finds a bug in v2.8.0 RC1 or newer, please post them here or open a new issue.
CC @GreyWyvern
The text was updated successfully, but these errors were encountered: