Latest Tesseract in Tika - tesseract

Newest available version of Tesseract is 5.x. but the latest tika is still using 4.x.
Is it possible to upgrade version of tesseractOCR in Tika?

We kept the 1.x branch alive for a year after cutting over to 2.x to
allow people time to migrate. Most of the changes in 1.x in the last
6 months or so have been security related. We will no longer support
1.x after September 30, 2022.
I've opened a ticket and PR to upgrade tesseract to 5.x in our next 2.x release -- 2.5.0.
https://issues.apache.org/jira/browse/TIKA-3860

Related

Rundeck GA version Compatibility

Currently I am using Rundeck 3.0.23-20190619.
Whether Rundeck 3.0.23-20190619 is stable version?
From the https://bintray.com/rundeck/rundeck-rpm/rundeck able to see the Rundeck 3.0.23-20190619 is not yet published as GA.
2.11.14-1.70.GA is the latest GA version with build date 2019-09-13T03:37:04.000Z.
Will the application developed with 3.0.23-20190619 compatible with 2.11.14-1.70.GA?
Right now the latest stable release is 3.1.2, you can check the latest version in the changelog here. The "GA" notation is not used anymore. In some cases, you can see some updates of 2.11 / 3.0 branches focused on backports, not for new features, etc.
Your projects and jobs are compatible using 2.11, 3.0 and 3.1 branches.

Can I publish a version older than the newest on NuGet?

Suppose I have version 1.1.0 on a NuGet server.
I then continue development and push version 1.2.0.
Then I find a bug in version 1.1.0 and want to fix this.
At this point, can I still push version 1.1.1?
There's nothing in the NuGet spec or protocol that prevents it, so it might depend on which NuGet server you're using, but I would be extremely surprised if any server forbids it because it would be so short sighted, in my opinion.
Using NuGet.Protocol on nuget.org as an example, version 4.9.3 was release in January 2019, but versions 4.8.2, 4.7.2, 4.6.3, 4.5.2, 4.4.2 and 4.3.1 were released in March, two months later.

PHP 7.2 not being updated from vulnerable 7.2.10?

The version of PHP 7.2 in the current Software Collection (version 3.2) is 7.2.10, which has a number of security vulnerabilities. From the release notes for upcoming version 3.3, it appears that SCL 3.3 will keep 7.2.10 unchanged. I don't understand this. PHP 7.2.11 was released in October 2018, and the latest release on PHP's 7.2 branch is 7.2.18. What is the recommendation for addressing these vulnerabilities if SCL is choosing not to keep up?

which codeigniter version I should use production and deprecated function

I am having one codeigniter application with version 2.2.6. Is it good to use it in production OR I have to upgrade to 3.1
If YES how to upgrade? Version 3.x is still under development. What are the deprecated function (https://www.codeigniter.com/docs)
Its always better to use latest version for speed & security purpose.
But first you have to check your server PHP version, because CodeIgniter latest version 3.1.9 is not compatible with PHP 5.6
Your server must have PHP version 7.1 or 7.2 for CI 3.1.x
For upgrade CodeIgniter 2.2.6 to 3.1.x, you have to make few changes.
You can get steps for upgrade CI from here.
If your projects is not using deprecated CI functionality, then just replace "system" folder with latest version of CI will work.
My suggestion is to use CI latest version in production.

Difference between wildfly 9.0.1 vs 8.2.1

I am seeing 2 versions (9.0.1 vs 8.2.1) of wildfly which were released on the same day. What is the difference between two versions and why there are 2 versions exist in parallel? I couldn't find it over the internet.
Wildfly ships on a very fast development cycle. Each major release 8.x, 9.x, 10.x contains major changes from the previous version. All current major work is being done on the 10.x beta versions.
The minor versions are for bugfixes related to that particular release. Since there are now people in production with both 8.x and 9.x, any critical bugs or security patches go into one of these releases. It is very possible a security issue could exist and be fixed in both 8.x.1 and 9.x.1.
JBoss EAP, which is based on WildFly, deliberately has a slower release schedule. For each major version they release they offer paid support for 4 years, so they change major versions much slower.
There is a good slide of the lifecycle of WildFly/JBoss on page 9 of this slide-deck from the RedHat Summit in June:
http://videos.cdn.redhat.com/summit2015/presentations/12186_red-hat-jboss-enterprise-application-platform-7-roadmap-new-features.pdf
Here is the official announcement for the pair of releases: -
http://wildfly.org/news/2015/07/23/WildFly-901-and-821/