Any plans to make new release? #3331

kloczek · 2021-03-15T20:28:00Z

I think that it would be good to flush currently committed changes and make new release :)

GuillemGSubies · 2021-03-16T08:18:47Z

I would love to see a new release too

Shreeshrii · 2021-03-17T12:10:45Z

Please see https://tesseract-ocr.github.io/tessdoc/Planning for some earlier notes.

amitdo · 2021-03-23T13:10:57Z

@stweil,

What about tagging a new alpha soon?

stweil · 2021-03-23T15:17:14Z

That's my plan. I just want to make sure that it does not contain major issues.

stweil · 2021-04-01T20:30:54Z

See new release.

kloczek · 2021-04-01T23:16:12Z

looks like it not reccomended to use as stable release. Am I right?
could you please concuder change tagging convention and not use dashesh in version string?
None of the packaging software allows use dashes in version string (simple iusing not standard versions strings adds kind of obstacle on automated packaging). With using only digits and dots exampl version string for alpha would be like 4,99.1 this would allow as well easy upgrade when 5.0.0 finally will be released :)

stweil · 2021-04-02T05:23:43Z

I recommend using the latest version of Tesseract because it is faster and has less errors than release 4.1.1. It is nevertheless tagged as alpha prerelease because there are still changes planned for API and functionality. Those changes don't affect most normal users of Tesseract.

The version string follows the rules for semantic versioning and should be easy to understand and parse. Ubuntu has much more complex package versions like 0.5.3+18.04.20180207.2-0ubuntu2 for example.

kloczek · 2021-04-02T12:05:43Z

Please be aware that tesseract is not only packaged by Ubuntu and not as well only Linux
If just released version is recommended as stable why not just vrersion it as 5.0.0?

stweil · 2021-04-02T14:50:24Z

If just released version is recommended as stable why not just version it as 5.0.0?

As soon as there is a 5.0.0, any more API changes would require to switch to 6.0.0, 7.0.0 and so on.

amitdo · 2021-04-02T15:33:11Z

Last release was in December 2019, and it was a partial backport from 5.0.0. In many workplaces, it is forbidden to use a version of software which is in "alpha" or "beta" state. Even outside of work environment, many users will stay away from "alpha" version. Many of our users are waiting for a new, improved release, which is not tagged as alpha/beta.

I suggest to release a new "final" 5.0.0 version in the next ~~30-90~~ 60-120 days.

My 2 cents...

stweil · 2021-04-06T16:29:28Z

I suggest to release a new "final" 5.0.0 version in the next 60-120 days.

So let's see how far we come with the to do issues from the Tesseract next project list.

egorpugin · 2021-04-06T18:38:08Z

Some of them are blocked by 5.0.0, so rational separation between 5 and 6 should be done.
My vote is to keep 5.0 small (current state is ok) and unblock 6.0 faster and 6.0 will have more changes.

amitdo · 2021-05-02T16:47:38Z

Can we move to 'beta' before the of this month?

amitdo · 2021-08-15T12:37:26Z

@stweil, when can we release 5.0 final? First step should be 5.0.0-beta.

stweil · 2021-08-15T15:23:04Z

I just tagged 5.0.0-beta-20210815.

stweil · 2021-08-15T19:20:47Z

Our milestone for 5.0.0 still includes 21 open issues.

We have to decide which of those issues should be fixed for the final 5.0.0 release and which issues can be fixed later, either in a 5.x.y or in a future release 6.

Please add your opinions at the different issue discussions.

zdenop · 2021-08-16T07:22:28Z

We are at the stage, that I suggest to use/test current master in case of any problem with version 4. Backport fixes and improvement from version 5 is not worthy of time and energy IMO. I am convinced we should release version 5 ASAP (e.g. in end of September to have change make inevitable fixes, tests and docs adjustments).

I would suggest to use following prioritization of issues:

Easy fixes ;-) (e.g. if somebody is working on something)
API changes (e.g. missing table extraction is really big topic)
General problem (e.g. changes related to only particular language /OS could be postponed)

amitdo · 2021-08-16T08:10:08Z

@zdenop or @stweil, could you announce the beta pre-release in the tesseract-ocr forum? Ask users to test it (or the master branch) and report about any regression in speed or accuracy compared to 4.1.1.

amitdo · 2021-08-17T16:01:43Z

https://groups.google.com/g/tesseract-ocr/c/pd_8B0wGBZc

Zdenko, thanks!

amitdo · 2021-08-18T20:32:16Z

https://www.phoronix.com/scan.php?page=news_item&px=Tesseract-5.0-Beta

stweil · 2021-08-18T20:50:36Z

https://twitter.com/stjoweil/status/1426142063167516672

stweil · 2021-08-18T20:52:44Z

Should we also make a new release 4.1.2, based on the current 4.1 branch or with additional backports (which ones)?

amitdo · 2021-08-18T22:20:22Z

I suggest to focus on 5.0.0 only.

egorpugin · 2021-08-18T22:25:56Z

Also I'd like to focus on future open-to-changes-master-branch and modernization efforts.

stweil · 2021-11-14T19:44:00Z

Should we also make a new release 4.1.2, based on the current 4.1 branch or with additional backports (which ones)?

Release 4.1.2 is now available.

stweil · 2021-11-15T08:11:45Z

I am sorry, but the 4.1.2 is broken (issue #3642). That was fixed in commit 28ad3e8. So we need a new release 4.1.3. Is there anything else which should be included in 4.1.3?

stweil · 2021-11-15T17:42:57Z

Release 4.1.3 is now available.

kloczek · 2021-11-15T20:02:31Z

LGTM :)
Thank you.

Closing.

amitdo · 2021-11-21T15:45:04Z

@stweil, what's the next step? Another RC or final 5.0.0 release? When?

stweil · 2021-11-21T19:15:41Z

Do you think that the release is good enough for a final 5.0.0? What would you suggest?

I just recently noticed a new bug #3655. And I still wait for reviews of pull request #3651 which is an API change, so must be merged in 5.0.0. Therefore a 5.0.0-rc3 might be reasonable.

amitdo · 2021-11-21T19:45:25Z

Do you think that the release is good enough for a final 5.0.0?

Yes.

I just recently noticed a new bug #3655.

Do you think you can fix it this week?

I still wait for reviews of pull request #3651 which is an API change, so must be merged in 5.0.0.

If you don't get a reply in the next few days, I suggest to merge this PR.

Therefore a 5.0.0-rc3 might be reasonable.

Okay, but let's release 5.0.0 this year...

egorpugin · 2021-11-21T19:58:33Z

You can post-fix any wanted issues into minor releases (5.1 or 5.0.1).

stweil · 2021-11-22T21:10:04Z

Release 5.0.0-rc3 is now available.

Hopefully we can release the final 5.0.0 still in November.

amitdo · 2021-11-24T05:30:29Z

@egorpugin,

IMO, we should test 5.0.0 with VS2022 and still test VS2019.

https://devblogs.microsoft.com/visualstudio/visual-studio-2022-now-available/

https://github.blog/changelog/2021-08-23-github-actions-windows-server-2022-with-visual-studio-2022-is-now-available-on-github-hosted-runners-public-beta/

https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md

egorpugin · 2021-11-24T11:17:24Z

See 6f399c0

stweil · 2021-11-30T14:56:21Z

I'd like to release 5.0.0 today (within the next few hours). Is there anything still missing for the release?

There are several open issues, but those can be addressed in 5.0.1 or 5.1.0.

Shreeshrii · 2021-11-30T17:06:48Z

Thank you @stweil and other contributors for 5.0.0.

stweil · 2021-11-30T17:38:04Z

There where nearly 70 contributors from 4.0 to 5.0.0, and about 30 of them had at least two contributions (commits). That's nice.

And of course thank you also to those who have sent helpful bug reports and suggestions as issues.

stweil · 2021-11-30T17:59:20Z

Release 5.0.0 is now available.

VV-KAR · 2021-12-01T15:31:08Z

Congrats on the release! Do you have an eta on the exe for 5.0.0? Thanks!

stweil · 2021-12-01T15:47:34Z

Do you mean https://github.com/UB-Mannheim/tesseract/wiki?

amitdo · 2021-12-01T17:02:14Z

5.x (post-5.0.0) and 6.x plans should be discussed in separate issues.

stweil · 2021-12-01T21:58:58Z

https://twitter.com/stjoweil/status/1465749015656644608
https://www.phoronix.com/scan.php?page=news_item&px=Tesseract-5.0-Released

Shreeshrii · 2021-12-02T06:02:30Z

The readme, documentation and tesstrain should also be updated for 5.0.0. Afterwards tessdoc and tesstrain should also be given a 5.0 version.

stweil · 2021-12-02T09:52:21Z

tessdata* also need new tags, but first we should review and fix some open issues.

Shreeshrii · 2021-12-05T01:37:25Z

Please see https://groups.google.com/g/tesseract-ocr/c/7nvw7qG8lWc/m/LnmSvFKDBQAJ

marco atzeri
Dec 4, 2021, 10:37:33 PM (8 hours ago) 
to [email protected]
Hi,

I am updating the cygwin package from 4.1.1 to 5.0.0
and I noticed that 3 scripts

language-specific.sh
tesstrain.sh
tesstrain_utils.sh

are not anymore in the source code.

Have they been replaced by something else that I should pack instead ?

Regards
Marco

amitdo · 2021-12-05T08:31:02Z

Release 4.1.3 is now available.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html-single/8.5_release_notes/index

Let's see if they will upgrade to 4.1.3 in RHEL 8.6, and if they will ship Tesseract 5.0.0 in RHEL 9.

amitdo · 2022-06-12T23:09:08Z

@stweil, can we close this issue?

I think 4.1.3 should be the last version in the 4.x series.

amitdo closed this as completed May 20, 2021

This comment has been minimized.

Sign in to view

amitdo reopened this Aug 16, 2021

amitdo added the RFC label Aug 16, 2021

kloczek closed this as completed Nov 15, 2021

amitdo reopened this Nov 15, 2021

amitdo closed this as completed Dec 1, 2021

amitdo unpinned this issue Dec 1, 2021

Shreeshrii reopened this Dec 2, 2021

stweil closed this as completed Jun 13, 2022

Any plans to make new release? #3331

Any plans to make new release? #3331

Comments

kloczek commented Mar 15, 2021

GuillemGSubies commented Mar 16, 2021

Shreeshrii commented Mar 17, 2021 • edited Loading

amitdo commented Mar 23, 2021

stweil commented Mar 23, 2021

stweil commented Apr 1, 2021

kloczek commented Apr 1, 2021

stweil commented Apr 2, 2021

kloczek commented Apr 2, 2021

stweil commented Apr 2, 2021

amitdo commented Apr 2, 2021 • edited Loading

stweil commented Apr 6, 2021

egorpugin commented Apr 6, 2021

amitdo commented May 2, 2021

amitdo commented Aug 15, 2021

stweil commented Aug 15, 2021

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

stweil commented Aug 15, 2021

zdenop commented Aug 16, 2021

amitdo commented Aug 16, 2021

amitdo commented Aug 17, 2021

amitdo commented Aug 18, 2021

stweil commented Aug 18, 2021

stweil commented Aug 18, 2021

amitdo commented Aug 18, 2021

egorpugin commented Aug 18, 2021

stweil commented Nov 14, 2021 • edited Loading

stweil commented Nov 15, 2021

stweil commented Nov 15, 2021

kloczek commented Nov 15, 2021

amitdo commented Nov 21, 2021

stweil commented Nov 21, 2021

amitdo commented Nov 21, 2021 • edited Loading

egorpugin commented Nov 21, 2021

stweil commented Nov 22, 2021 • edited Loading

amitdo commented Nov 24, 2021

egorpugin commented Nov 24, 2021

stweil commented Nov 30, 2021 • edited Loading

Shreeshrii commented Nov 30, 2021

stweil commented Nov 30, 2021 • edited Loading

stweil commented Nov 30, 2021

VV-KAR commented Dec 1, 2021

stweil commented Dec 1, 2021

amitdo commented Dec 1, 2021 • edited Loading

stweil commented Dec 1, 2021

Shreeshrii commented Dec 2, 2021

stweil commented Dec 2, 2021

Shreeshrii commented Dec 5, 2021

amitdo commented Dec 5, 2021

amitdo commented Jun 12, 2022

Shreeshrii commented Mar 17, 2021 •

edited

Loading

amitdo commented Apr 2, 2021 •

edited

Loading

stweil commented Nov 14, 2021 •

edited

Loading

amitdo commented Nov 21, 2021 •

edited

Loading

stweil commented Nov 22, 2021 •

edited

Loading

stweil commented Nov 30, 2021 •

edited

Loading

stweil commented Nov 30, 2021 •

edited

Loading

amitdo commented Dec 1, 2021 •

edited

Loading